Add implementation of dpnp.nextafter function
#1938
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
6 tasks
Contributor
|
View rendered docs @ https://intelpython.github.io/dpnp/index.html |
vtavana
reviewed
Jul 23, 2024
github-actions bot
added a commit
that referenced
this pull request
Jul 23, 2024
* Implement dpnp.nextafter * Add MKL extension for nextafter * Applied pre-commit hook * Applied review comments 7b016d9
Sign up for free
to 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.
The PR proposes to add implementation of
dpnp.nextafterfunction which is missing now.There is new VM functions are added to use
nextafterfrom OneMKL library where it's possible.In other places the PR propose to leverage on new binary universal function
_nextafterfunction from dpctl implemented in dpctl-1730.The all affected tests are updated to cover different use cases.