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
The scope types include "class name" and "funk name" to match the names in, e.g., class and function declarations. However, it does not include a "type name" to match the name in a type declaration. I propose we add such a scope type.
We've actually been considering deprecating "funk name" and "class name" as they're now almost completely equivalent to just chaining modifiers: "name funk" and "name class". They're a holdover from before modifiers could be chained. See #1518 for more discussion
I could see a consistency argument for supporting "type name" if we support "class name", but note that these scope types technically introduce ambiguity because "type name" could be parsed as a modifier chain: select name then select type
The scope types include "class name" and "funk name" to match the names in, e.g., class and function declarations. However, it does not include a "type name" to match the name in a type declaration. I propose we add such a scope type.
The text was updated successfully, but these errors were encountered: