Get_count: Return nothing on failure - #976
Open
eschnett wants to merge 3 commits into
Open
Conversation
Return `nothing` instead of the (ABI-dependent) integer value `MPI_UNDEFINED` on failure. Add explicit checks for `nothing` in the caller. (Previously there was no error handling there.)
Member
|
This is technically a breaking change |
Contributor
Author
|
Yes, technically it is breaking. But I want to argue that the previous state was ill-defined: Returning Also, all other similar functions already return |
Contributor
Author
|
@vchuravy is your 👍 approval for this PR? |
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
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.
Return
nothinginstead of the (ABI-dependent) integer valueMPI_UNDEFINEDon failure.Add explicit checks for
nothingin the caller. (Previously there was no error handling there.)