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
Full name of submitter (unless configured in github; will be published with the issue): Jim X
Consider this example
structA{
autof(){
g();
}
autog(){}
};
The compiler says
use of 'auto A::g()' before deduction of 'auto'
The justification might be [dcl.spec.auto.general] p13. However, it's unclear what function whose return type is considered as undeduced.
Suggestion Resolution:
A function whose return type contains placeholder type at point P is considered undeduced if its definition is not reachable.
The text was updated successfully, but these errors were encountered:
xmh0511
changed the title
[dcl.spec.auto.general] p13 What function whose return type is considered as undeduced?
[dcl.spec.auto.general] p13 What is a function whose return type is considered as undeduced?
Jan 3, 2025
This is the "complete class context" question, and how exactly (in which order) class bodies and member function bodies are parsed.
According to [class.mem.general] p8, the body of A::f is complete class context, and the name lookup finds the declaration from the class-specifier of A as per [class.member.lookup] p3. It is unclear whether the declaration found from the class-specifier is considered undeduced.
Full name of submitter (unless configured in github; will be published with the issue): Jim X
Consider this example
The compiler says
The justification might be [dcl.spec.auto.general] p13. However, it's unclear what function whose return type is considered as undeduced.
Suggestion Resolution:
The text was updated successfully, but these errors were encountered: