Uh oh!
There was an error while loading. Please reload this page.
Clarify expected values in ones and ones_like when dtype is a complex number data type - #438
Merged
Conversation
…omplex number data type
kgryte
commented
Jun 6, 2022
ContributorAuthor
As this PR has received approval and the changes are straightforward, will go ahead and merge... |
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
onesandones_likeconcerning expected output values whendtypeis eithercomplex64orcomplex128. Namely, only real components are ones. Imaginary components are zero for all elements.