Add proper handling of NaN values in dpnp.unique
implementation with axis not None
#1989
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.
The PR addresses the comment from gh-1972 and implements a proper handling of NaN values in all use cases.
Note, that the result may vary towards numpy in case of complex dtype, because for complex all possible NaNs are considered equivalent (i.e.
complex(nan, 1)
,complex(2, nan)
andcomplex(nan, nan)
are the same).