You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In talking with Jason Merrill about wording for a paper, we noticed that we have several terms that are some kind of immediate noun:
immediate subexpression
immediate subobject
immediate scope
immediately-declared constraint
immediate function
immediate invocation
immediate-escalating (expression or function)
In the [expr.const] section, immediate functions, immediate invocations, and immediate-escalating expressions and functions are closely related to each other. "Immediate" here means "now." But that's not really the same meaning of "immediate" as in the other terms.
In the others, I wonder if an adjective like "direct" would simply be better. Your direct subexpressions and subobjects, your direct scope? We actually already talk about direct members and direct base classes, so direct subobjects and direct subexpressions makes sense.
The text was updated successfully, but these errors were encountered:
I agree that we should say "direct subexpression".
The one use of "immediate subobject" is in https://eel.is/c++draft/class.union.general#5 and I'm not sure why it doesn't just say "direct member", or even just "member" (since a union can't have inherited members).
I don't like "direct scope". How about "proximate scope"?
In talking with Jason Merrill about wording for a paper, we noticed that we have several terms that are some kind of immediate noun:
In the [expr.const] section, immediate functions, immediate invocations, and immediate-escalating expressions and functions are closely related to each other. "Immediate" here means "now." But that's not really the same meaning of "immediate" as in the other terms.
In the others, I wonder if an adjective like "direct" would simply be better. Your direct subexpressions and subobjects, your direct scope? We actually already talk about direct members and direct base classes, so direct subobjects and direct subexpressions makes sense.
The text was updated successfully, but these errors were encountered: