Skip to content

Conversation

Quuxplusone
Copy link
Contributor

[util.smartptr.shared.const] defines the phrase "enables shared_from_this" without a \defnx entry.

[optional.general] used \defnx when defining the phrase "contains a value", but [variant.general] does not \defnx the phrase "holds a value"; let's be consistent, and I think this is the right direction in which to be consistent.

[container.alloc.reqmts] has many instances of "T is foo means that...", which should be either "T is foo if..." or else "[The phrase] T is foo means that...". The proposed resolution of LWG 2158 is related, in that it currently says "Syntactic requirements of T is foo" when what it means is "Syntactic requirements of T is foo" (use-mention distinction).

Happy to split this into separate PRs, but I figure the same grammar-lawyers will be interested in all three.

Makes [optional.general] consistent with [variant.general],
which does not italicize "holds a value of alternative type T".
There are two possible fixes here. Either
> \tcode{T} is \defnx{\oldconcept{DefaultInsertable} into \tcode{X}} if...
or
> \defnx{\tcode{T} is \oldconcept{DefaultInsertable} into \tcode{X}} means that...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant