Don't define typedef-names in the library wording #6419
Conversation
frederick-vs-ja
force-pushed
the
declare-typedef-names
branch
2 times, most recently
from
46aa0dc
to
ed407e0
Compare
wg21bot
added
the
needs rebase
frederick-vs-ja
force-pushed
the
declare-typedef-names
branch
from
ed407e0
to
dd1a092
Compare
This comment was marked as resolved.
This comment was marked as resolved.
jensmaurer
removed
the
needs rebase
|
I'm very much on board with replacing "defined" with "declared" when we're talking about the introduction of a name, such as "X is declared if and only if..." I think that's a straightforward fix and actually improves the presentation quite a bit. For situations where we describe what the "value" of a typedef is, I like "defined" a bit better, because it's alluding to the mathematical idea of "definition", and that's what we do in those contexts. A better way of phrasing this without using the term "defined" might exist, but "determined" leaves open a bit who determines what. Maybe "specified to be" would work; I'm not sure. Anyway, if you want to extract the changes of the first category into a separate pull request, where we actually talk about the (presence of) a typedef declaration, then that could probably progress faster. |
frederick-vs-ja
force-pushed
the
declare-typedef-names
branch
from
dd1a092
to
9bab345
Compare
|
@jensmaurer Now the changes to "determined" are reverted. |
Also mention [re].
In the example, it seems a bit verbose to say "declarations and definitions".
Use "declare" instead.
Use "declare" instead.
Use declared" instead.
Use "declare" instead.
Use "declare" instead.
Use "declare" instead.
Use "declare" instead.
Use "declare" instead.
Use "declare" instead.
Use "declare" instead.
frederick-vs-ja
force-pushed
the
declare-typedef-names
branch
from
9bab345
to
ddd5f43
Compare
Since (non-template) typedef-names are declared but not defined ([basic.def]/2.9, [basic.def]/2.10).
value_type(or sometimestype?) is not always a typedef-name, but it is in most case. So, I'm changing to use "declared" for it.iterator_categoryanditerator_concept, this PR used to use "determined" instead of "defined" when the aliased type is talked. Now the changes to "determined" are reverted.