[mdspan.extents.cons] "constexpr" should precede "explicit" #5947
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
In library function declarations, the `constexpr` specifier always precedes the `explicit` specifier per our standing style guide.
|
It's correct in the class body, but not in the itemdecl. |
|
What prevented the check script from noticing this? |
The fact that the script doesn't check for this, which I've attempted to remedy with #5948. |
|
Oh, I thought there already was such a check in place. Probably because Clang Format already does this. |
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.
In library function declarations, the
constexprspecifier always precedes theexplicitspecifier per our standing style guide.