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

Nested tuple literal should have a type and converted type #12623

Closed
jcouv opened this issue Jul 19, 2016 · 1 comment
Closed

Nested tuple literal should have a type and converted type #12623

jcouv opened this issue Jul 19, 2016 · 1 comment
Assignees
Labels
Area-Compilers Feature - Tuples Tuples Resolution-Not Reproducible The described behavior could not be reproduced by developers

Comments

@jcouv
Copy link
Member

jcouv commented Jul 19, 2016

In the following test, the tuple literal (1, 2) should have a type and a converted type

        [Fact]
        public void TypeMergingSuccess3()
        {
            string source = @"
class C
{
    static void Main()
    {
        (string x1, var x2) = (null, (1, 2));
        System.Console.WriteLine(x1 + "" "" + x2);
    }
}
";

#12526 (comment)

@jcouv
Copy link
Member Author

jcouv commented Aug 12, 2016

Turns out this was a bug in the test code (looking at the argument syntax node, instead of the tuple literal syntax node. Updated TypeMergingSuccess3.

@jcouv jcouv closed this as completed Aug 12, 2016
@jcouv jcouv added the Resolution-Not Reproducible The described behavior could not be reproduced by developers label Aug 12, 2016
jcouv added a commit to jcouv/roslyn that referenced this issue Aug 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Compilers Feature - Tuples Tuples Resolution-Not Reproducible The described behavior could not be reproduced by developers
Projects
None yet
Development

No branches or pull requests

1 participant