-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Inference failure for tuple type vs tuple underlying type (regression) #20583
Labels
Area-Compilers
Blocked
Bug
Feature - Tuples
Tuples
Tenet-Compatibility
Violation of forwards/backwards compatibility in a design-time piece.
Milestone
Comments
gafter
added
Area-Compilers
Bug
Tenet-Compatibility
Violation of forwards/backwards compatibility in a design-time piece.
labels
Jun 30, 2017
gafter
added a commit
to gafter/roslyn
that referenced
this issue
Jun 30, 2017
Fixes dotnet#20494 Adds a test for dotnet#20583
A regression test is being added for this (skipped) in #20587. |
I did not test whether or not this bug is present for VB. |
This bug is present for VB as well. The following program compiles in earlier versions of VS, but not in VS 2017. Public Class C
Public Shared Sub Main()
Dim b = New ValueTuple(Of Integer, Integer, Integer, Integer, Integer, Integer, Integer, ValueTuple(Of Integer))()
M1(b)
End Sub
Public Shared Sub M1(Of T1, T2, T3, T4, T5, T6, T7, TRest As Structure)(x As ValueTuple(Of T1, T2, T3, T4, T5, T6, T7, TRest))
End Sub
End Class |
This would likely be fixed as a side-effect of #20648 |
AlekseyTs
added a commit
to AlekseyTs/roslyn
that referenced
this issue
Sep 22, 2017
…wards compatibility break. Fixes dotnet#20583.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area-Compilers
Blocked
Bug
Feature - Tuples
Tuples
Tenet-Compatibility
Violation of forwards/backwards compatibility in a design-time piece.
The following correct program compiles successfully in VS2015, but fails to compile in VS2017:
with the following error
The text was updated successfully, but these errors were encountered: