P2996R13 Reflection for C++26 #8008
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
|
Fixed link, thanks. |
|
We could certainly move all the commits into a single PR and the test and review that again. Let's wait for a first round of reviews on both current PRs to settle, then we'll take it from there. |
|
@tkoeppe by the way, you've put the milestone date for 2025-06 as 06-31. Is that actually correct? I was under the impression that we would want to have the updated working draft in the post-Sofia mailing, if not sooner so that the ISO review process can start ASAP. |
|
@Eisenwave Sorry, no idea, I don't recall making that label or how it was made. Don't worry about it. We're not going to stop the process because of what a label says. |
|
That milestone is by me. I've moved the date to 07-15. |
| If the candidates are denoted by a \grammarterm{splice-expression}, | ||
| then $S$ shall not be a block scope. | ||
| \item | ||
| The default arguments used in the call \tcode{C} are |
There was a problem hiding this comment.
As discussed offline, probably should have been "the call to C".
There was a problem hiding this comment.
@jensmaurer Is that OK as an editorial follow-up? It's not in the paper.
1f97ede to
dec16ef
Compare
dec16ef to
f07c133
Compare
| %FIXME: \libheaderref{meta} after renaming to meta.syn | ||
| \libheaderrefx{meta}{meta.type.synop}, |
| Unless \tcode{\placeholder{F}} is designated an addressable function, | ||
| it is unspecified if or how | ||
| a reflection value designating the associated entity can be formed. | ||
| %FIXME: Why is this not an example, but a note that begins with "For example"? |
There was a problem hiding this comment.
We occasionally do that. Note there is no actual code in this note/example, so I'm fine with this being a note. It's equally fine to use begin{example} and strike "For example," in the text.
| %but I read between the lines and took editorial liberty to create it. | ||
| \rSec1[meta.reflection]{Reflection} | ||
|
|
||
| %FIXME: Jens said this should be [meta.syn] |
There was a problem hiding this comment.
Yes, please. All headers (historic accidents notwithstanding) should be name.syn; it simplifies macro usage pointing to them so much.
| @@ -2554,6 +2570,3461 @@ | |||
| \end{example} | |||
| \end{itemdescr} | |||
|
|
|||
| %FIXME: The paper doesn't actually specify that this subclause should exist, | |||
There was a problem hiding this comment.
Sounds good, except that'd like to have a global rename of "meta.reflection*" labels to "meta.refl*" for space economy (without loss of clarity, in my view).
| \indexheader{meta}% | ||
|
|
||
| \begin{codeblock} | ||
| %FIXME: I see the same in <algorithm> with a // see \ref{initializer.list.syn} comment |
There was a problem hiding this comment.
yes, let's have the "see"
| %FIXME: why are we suddenly starting to use math symbols for T | ||
| %when the previous paragraph did not? |
There was a problem hiding this comment.
We should not. Types in particular are always code font. Please fix.
| %FIXME: why are we suddenly starting to use math symbols for T | ||
| %when the previous paragraph did not? | ||
| \tcode{tuple_size_v<$T$>} | ||
| %FIXME: comma. |
| A reflection representing | ||
| the type denoted by \tcode{tuple_element_t<$I$, $T$>}, | ||
| where $T$ is th type represented by \tcode{dealias(type)} | ||
| %FIXME: comma. |
| \pnum | ||
| \returns | ||
| \tcode{variant_size_v<$T$>} | ||
| %FIXME: comma |
| \returns | ||
| A reflection representing the type denoted by | ||
| \tcode{variant_alternative_t<\brk{}$I$, $T$>} | ||
| %FIXME: comma |
Feel free to cherry-pick into #8004 once @Eisenwave is done with the library part.