-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Tests needed for out variables in declarators in for loop. #13459
Labels
Area-Compilers
Bug
New Language Feature - Out Variable Declaration
Out Variable Declaration
New Language Feature - Pattern Matching
Pattern Matching
Milestone
Comments
gafter
added
Area-Compilers
Test
Test failures in roslyn-CI
New Language Feature - Pattern Matching
Pattern Matching
New Language Feature - Out Variable Declaration
Out Variable Declaration
labels
Aug 30, 2016
I think there is actually a bug in this scenario. |
AlekseyTs
added a commit
to AlekseyTs/roslyn
that referenced
this issue
Sep 1, 2016
…rSyntax.ArgumentList in ‘fixed’, ‘for’ and ‘using’ statements. Related to dotnet#12597. Fixes dotnet#13459, dotnet#13460.
AlekseyTs
added
4 - In Review
A fix for the issue is submitted for review.
and removed
3 - Working
labels
Sep 1, 2016
AndyGerlicher
removed
4 - In Review
A fix for the issue is submitted for review.
Bug
labels
Sep 2, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area-Compilers
Bug
New Language Feature - Out Variable Declaration
Out Variable Declaration
New Language Feature - Pattern Matching
Pattern Matching
In #13274 (comment) @AlekseyTs asked about test coverage for the error case of out variables and pattern variables (illegally) declared in declarators in a for loop. We should ensure we have such tests to ensure the compiler behavior is sane.
See also #13274 (comment)
The text was updated successfully, but these errors were encountered: