[ 2015-10, Kona Saturday afternoon ]
GR: I cannot figure out what "exposition only" means. JW explained it to me once as meaning that "it has the same normative effect as if the member existed, without the effect of there actually being a member". But I don't know what is the "normative effect of the existence of a member" is.
MC: The "exposition-only" member should be private. GR: But it still has normative effect.
GR, STL: Maybe the member is public so it can be used in the public section? WEB (original worder): I don't know why the member is public. I'm not averse to changing it. GR: A telecon instructed me to find out how [exposition-only] is used elsewhere, and I came back with this issue because I don't understand what it means.
STL: We use exposition-only in many places. We all know what it means. GR: I don't know precisely what means.
STL: I know exactly what it means. STL suggests a rewording: the paragraph already says what we want, it's just a little too precise. GR not sure.
WEB: Are there any non-members in the Standard that are "exposition only"? STL: DECAY_COPY and INVOKE.
GR: There are a few enums.
HH: We have nested class types that are exposition-only. HH: We're about to make "none_t" an exposition-only type. [Everyone lists some examples from the Standard that are EO.] GR: "bitmask" contains some hypothetical types. That potentially contains user requirements (since regexp requires certain trait members to be "bitmask types").
STL: What's the priority of this issue? Does this have any effect on implementations? Is there anything mysterious that could happen?
AM: 2.
STL: How did that happen? It's at best priority 4. We have so many better things we could be doing.
WEB: "exposition only" in [???] is just used as plain English, not as words of power. GR: That gives me enough to make wording to fix this.
STL: I wouldn't mind if we didn't fix this ever.
MC: @JW, please write up wording for 2310 to make the EO members private. JW: I can't do that, because that'd make the class a non-aggregate.
WEB: Please cross-link both issues and move 2516 to "open".