[ranges.syn] remove trailing -> see below return type from three `t…
#5419
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
…o` overloads Since there is actually no return type specification to see below in [range.utility.conv].
jensmaurer
approved these changes
Apr 27, 2022
|
@jwakely , what do you think? |
|
@jwakely, ping. |
jwakely
approved these changes
May 4, 2022
There was a problem hiding this comment.
If we want to use -> decltype(see below) in the synopsis we should also do it in the detailed descriptions, and we don't do it there. This makes it consistent (and I don't think it would be an improvement to be consistent in the other direction by adding the trailing return type to the detailed descriptions).
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.
…o` overloads
Since there is actually no return type specification to see below in [range.utility.conv].