Parsing ahead for 'for' and 'foreach' ambiguities should recognize deconstructions

[jcouv]

        [Fact(Skip = "PROTOTYPE(tuples)")]
        public void ConfusedForWithDeconstruction()
        {
            var text = "for ((int x, var (y, z)) in foo) { }";
            var statement = SyntaxFactory.ParseStatement(text, offset: 0, options: TestOptions.Regular.WithTuplesFeature());

            // This expectation is wrong. We should expect a foreach statement (because the 'in' keyword is there)
            Assert.True(statement.Kind() == SyntaxKind.ForStatement);
        }

[jcouv]

FYI for @gafter

[jcouv]

I think it's unlikely we'll end up doing this. Closing.

[gafter]

There remains a skipped test with this issue ID.