ignore type symbols in lookup when enum type is expected #23694
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #23689
When an identifier expression expects an enum type, when looking up the identifier as a symbol, type symbols are ignored, i.e.
will give an "undeclared identifier" error. This is to make #23689 work in the least obtrusive way, it might cause other problems. It could also be generalized to all concrete types (
expected.kind in ConcreteTypes
instead of== tyEnum
).