Clarify overflow behavior in asarray
#409
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kgryte
added
Narrative Content
oleksandr-pavlyk
approved these changes
Mar 24, 2022
|
As this PR has received 3 approvals, will merge. Any further updates can be addressed in follow-up PRs... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR
asarrayconcerning what happens when an input value exceeds the precision of the resolved output array data type. Namely, behavior is left unspecified and, thus, implementation-defined. This follows similar guidance as found infull.fullandfull_likethat overflow behavior is implementation-defined even whendtypeis notNone.