Uh oh!
There was an error while loading. Please reload this page.
Add complex number support to APIs for returning unique elements - #540
Merged
Conversation
rgommers
approved these changes
Dec 13, 2022
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
unique_all,unique_counts,unique_inverse, andunique_values. This PR builds on Add complex number support toequal#528. Namely, by convention, equality is determined by independently comparing real and imaginary components respectively and then performing a logical AND (i.e., ifx = a + bjandy = c + dj, thenx == yiffa == c AND b == d.NaNbe considered unique.equal#528, this PR does not support the one-infinity model (see C99) where complex infinites are treated as equal.