Skip to content

[flat.{map,multimap,set,multiset}] Harmonize wordings in "The effect of calling..."#8212

Open
Quuxplusone wants to merge 1 commit into
cplusplus:mainfrom
Quuxplusone:flatmeowub
Open

[flat.{map,multimap,set,multiset}] Harmonize wordings in "The effect of calling..."#8212
Quuxplusone wants to merge 1 commit into
cplusplus:mainfrom
Quuxplusone:flatmeowub

Conversation

@Quuxplusone

Copy link
Copy Markdown
Contributor

Noticed this in the review of P3567 "flat_meow fixes" today; and this is not one of the things that it's going to fix, so might as well do it editorially first.

The egregious editorial issue here is that one place says "a container, containers, or range that is not sorted with respect to key_comp()," and another place says "a container, containers, or range that are not sorted with respect to key_comp()." We should fix the latter. Drive-by harmonize the exact wording and the line-breaks in each similar sentence:

"The effect of calling a meow"
"that has this property"
"with these arguments"
"is undefined".

Comment thread source/containers.tex Outdated
that is not sorted with respect to \tcode{key_comp()}, or
that contains equal elements,
that takes a \tcode{sorted_unique_t} argument
with a container, containers, or range that is not sorted with respect to \tcode{key_comp()}, or that contains equal elements,

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe a "container" is a "range," so should this (and throughout) just say "with a range or ranges that (is/are)...", "with a range or containers that (is/are)...", or any variation along those lines? I wasn't able to come up with a phrasing that wasn't icky. IMO the benefit of not-too-awful grammar is worth the cost of redundancy here.

Comment thread source/containers.tex Outdated
Comment thread source/containers.tex Outdated
Comment thread source/containers.tex Outdated
@wg21bot wg21bot added the needs rebase The pull request needs a git rebase to resolve merge conflicts. label Oct 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs rebase The pull request needs a git rebase to resolve merge conflicts.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants