Clarify output dtype guidance for mean, var, and std
#260
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
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
clarifies output dtype guidance for
mean,var, andstd, as discussed in gh-202.Notably, the PR adds notes which clarify the output array dtype when the input array has an integer dtype. While integer dtypes are not explicitly supported by the standard (due to mixed-type promotion being undefined), this PR adds language to require that, if an array having an integer dtype is provided, the returned array must have the default floating-point dtype.
For floating-point input arrays, the returned array must have the same dtype as the input array.