[range.adaptors] Make the prints message format consistent #5383
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.
Currently
<ranges>
has two formats for the description of print messages, one is// prints: 1 2 3 4 5 6 7 8 9
The other is
// prints \tcode{1 2 3 4 5 6 7 8 9}
This pull request converts all the first form to the second form, that is, omits the colon after
prints
, and then outputs the message in code format.It also fixes incorrect formatting of
The above prints:
in [range.join.with.overview][range.chunk.overview], [range.chunk.by.overview].