[function.objects] Use formal Returns: clause for std functors #909
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
Revise presentation of all functors in clauses 20.14.(5-8) to use a formal Returns: clause, consistent with the conventions laid out in clause 17, rather than ad-hoc presentation lacking any of the recognised markers. This turned into a substantial re-render. In order to break up a wall of code with occasional normative text, I have introduced a subsection for each class. Under each new subsection, I collect the primary class template and the 'diamond' specialization, which were previously separated by the intervening classes. I believe these changes are strictly editorial, but please let me know soon if you would rather see a CD ballot comment before accepting an editorial change of this scale.
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.
Revise presentation of all functors in clauses 20.14.(5-8) to use a
formal Returns: clause, consistent with the conventions laid out in
clause 17, rather than ad-hoc presentation lacking any of the
recognised markers.
This turned into a substantial re-render. In order to break up a
wall of code with occasional normative text, I have introduced a
subsection for each class. Under each new subsection, I collect
the primary class template and the 'diamond' specialization, which
were previously separated by the intervening classes.
I believe these changes are strictly editorial, but please let me
know soon if you would rather see a CD ballot comment before
accepting an editorial change of this scale.