[sequences.general] Promote header synopses to rSec2 #560
Conversation
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
Contributor
|
See also PR 478, which subsumes this change. |
Contributor
|
@jwakely: No weedier than |
zygoloid
added a commit
that referenced
this pull request
Nov 20, 2015
[sequences.general] Promote header synopses to sections
Member
|
This leaves us with around half of the header synopses in their own sections and half not (28 versus 29); it'd be nice to consistently provide a separate section for each header. |
Contributor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
In #357 @tkoeppe suggested this change. It would be more consistent with the rest of Clause 23, although it makes 23.3.1 [sequences.general] a rather weedy subclause.