[utility.arg.requirements] Break down requirement tables #6941
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
Member
|
This should be reviewed by LWG. |
Break down the requirements tables into regular specification text, following the lead of breaking down the container requirements. This also solves the problem of floating tables floating into unrelated clauses, as there will be no more floating tables.
AlisdairM
force-pushed
the
TextifyRequirementsTables
branch
from
e7dfaf9 to
2e6f0fe
Compare
wg21bot
added
the
needs rebase
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.
Fixes #6033, late, but as promised.
First draft that will probably need some consistent rewording.
Break down the requirements tables into regular specification text, following the lead of breaking down the container requirements. This also solves the problem of floating tables floating into unrelated clauses, as there will be no more floating tables.
For simplicity, new subsections have the same stable label as the table they replace, which simplifies the diff but are probably not the best names.