Bug 23144 – False circular reference error when the field name of a struct or class is the same as the type name

False circular reference error occurs when the field name of a struct or class is the same as the type name of the field. This error doesn't occur on local variables. --- module example; struct S { } struct OtherStruct { S s; // allowed S S; // Error: circular reference to variable `example.OtherStruct.S` } class C { } class OtherClass { C c; // allowed C C; // Error: circular reference to variable `example.OtherClass.C` } int main() { S S; // allowed C C; // allowed return 0; }

The message is not wrong: a lookup for `S` in `OtherStruct` begins in the `OtherStruct` scope so it finds `S` as a member, which is not ready yet. The module scope operator should be used here or a fully qualified type. ``` struct S { } struct OtherStruct { .S s; .S S; } ``` For local variables that works without qualifier because out of order declarations are not supported and the lookup is only valid for everything that is declared before the variable S (and then in the parent scopes) ``` int main() { S S; return 0; } ``` I suggest to close a invalid is the explanations are correct.

however the error message should rather be "S is used as a type", in that case the issue is valid.