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
either the local entity is not *this, or an enclosing class or non-lambda function parameter scope exists and, if the innermost such scope is a function parameter scope, it corresponds to a non-static member function, and
Since the wording "correspond" has been used to expound the relationship between one declaration and another declaration. Moreover, expounding the relationship between a declaration and a relevant scope, we use the "introduce", which is shown as the following:
every other scope S is introduced by a declaration, parameter-declaration-clause, statement, or handler (as described in the following subclauses of [basic.scope]) appearing in another scope which thereby contains S.
Hence, I think that change "it corresponds to a non-static member function" to that
it is introduced by a non-static member function
or
it is introduced by the parameter-declaration-clause of a non-static member function
is more precise and consistent.
The text was updated successfully, but these errors were encountered:
xmh0511
changed the title
[basic.def.odr#9] Saying A scope corresponds to a function is not precise
[basic.def.odr#9] Saying a scope corresponds to a function is not precise
Jul 23, 2021
xmh0511
changed the title
[basic.def.odr#9] Saying a scope corresponds to a function is not precise
[basic.def.odr#9] Saying that a scope corresponds to a function is not precise
Jul 23, 2021
[basic.def.odr#9]
Since the wording "correspond" has been used to expound the relationship between one declaration and another declaration. Moreover, expounding the relationship between a declaration and a relevant scope, we use the "introduce", which is shown as the following:
Hence, I think that change "it corresponds to a non-static member function" to that
or
is more precise and consistent.
The text was updated successfully, but these errors were encountered: