Fix two MPI_T enums #30
Merged
Conversation
This file contains 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
Per discussion in Tools WG session 18MAR, these should both logically be bitfields: CB_REQUIRE should be 0/1/3/7 as each level inherits the requirements of the previous at present but that's not a guarantee for the future, and verbosity should allow future expansion via bitmasking of both audience and level of detail.
dalcinl
approved these changes
Mar 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Per discussion in Tools WG session 18MAR, these should both logically be bitfields: CB_REQUIRE should be 0/1/3/7 as each level inherits the requirements of the previous at present but that's not a guarantee for the future, and verbosity should allow future expansion via bitmasking of both audience and level of detail.