Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CheckFeatureAvailability should not have side-effects on binding via hasErrors in ForEachLoopBinder #65363

Closed
jcouv opened this issue Nov 11, 2022 · 0 comments · Fixed by #65366
Assignees
Labels
Area-Compilers Concept-Design Debt Engineering Debt, Design Debt, or poor product code quality
Milestone

Comments

@jcouv
Copy link
Member

jcouv commented Nov 11, 2022

We should remove the side-effect on hasErrors in hasErrors |= !messageId.CheckFeatureAvailability( ... because some checks are conditional on hasErrors.

#65352 (comment)

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Compilers untriaged Issues and PRs which have not yet been triaged by a lead labels Nov 11, 2022
@jcouv jcouv self-assigned this Nov 11, 2022
@jcouv jcouv added Concept-Design Debt Engineering Debt, Design Debt, or poor product code quality and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Nov 11, 2022
@jcouv jcouv added this to the 17.5 milestone Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Compilers Concept-Design Debt Engineering Debt, Design Debt, or poor product code quality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant