-
-
Notifications
You must be signed in to change notification settings - Fork 15k
expected expression, found .. #105634
Copy link
Copy link
Closed
Labels
A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lintsC-bugCategory: This is a bug.Category: This is a bug.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.relnotesMarks issues that should be documented in the release notes of the next release.Marks issues that should be documented in the release notes of the next release.
Metadata
Metadata
Assignees
Labels
A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lintsC-bugCategory: This is a bug.Category: This is a bug.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.relnotesMarks issues that should be documented in the release notes of the next release.Marks issues that should be documented in the release notes of the next release.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Given the following code:
The current output is:
..is a valid expression (aRangeFullliteral), so this error is misleading. It should at a minimum have a suggestion to replace with the valid version&(..), and probably should just work. It also imho ideally shouldn't be a hard parser error blocking semantic passes; the parse of&(..)is fairly unambiguously intended, even if we decide we should still require the parenthesis.