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
[...] If the function is a non-static member function, the this parameter of the function is initialized with a pointer to the object of the call, converted as if by an explicit type conversion.
Seems to be some forgotten wording, the correct term would be "implicit object parameter".
A potential problem regarding this could be that it would be unclear if the lifetime of the object denoted by the object expression is extended by the reference binding, or if it follows the rules of a normal temporary, however in both these cases the lifetime would end at the completion of the full-expression, so it seems to be a non-issue save for the clarity.
The text was updated successfully, but these errors were encountered:
While I agree that "this parameter" is bad phrasing, the term "implicit object parameter" is only used during overload resolution as a technical conveyance, and does not seem to exist outside of overload resolution.
Editorial meeting: Express the desired offset adjustment semantics by more directly referring to [expr.prim.this] phrasing. Have CWG check the resulting wording.
[expr.call] p7 states:
Seems to be some forgotten wording, the correct term would be "implicit object parameter".
A potential problem regarding this could be that it would be unclear if the lifetime of the object denoted by the object expression is extended by the reference binding, or if it follows the rules of a normal temporary, however in both these cases the lifetime would end at the completion of the full-expression, so it seems to be a non-issue save for the clarity.
The text was updated successfully, but these errors were encountered: