LINQ immediate query execution not caught for type checking

Environment data

dotnet --info output: .NET Command Line Tools (1.0.0-preview2-1-003177)

Product Information: Version: 1.0.0-preview2-1-003177 Commit SHA-1 hash: a2df9c2576

Runtime Environment: OS Name: ubuntu OS Version: 16.04 OS Platform: Linux RID: ubuntu.16.04-x64

VS Code version: Version 1.9.1 Commit f9d0c687ff2ea7aabd85fb9a43129117c0ecf519 Date 2017-02-08T23:44:55.542Z Shell 1.4.6 Renderer 53.0.2785.143 Node 6.5.0

C# Extension version: 1.7.0

Steps to reproduce

Make a LINQ interrogation over a array, using an immediate query execution operator: ToArray

        public static void Main(string[] args)
        {
            int[] fib = new [] {0,1,1,2,3,5};
            IEnumerable<int> fib2 = fib.Where(x => x > 2).ToArray();
            Console.WriteLine($"{fib2[0]");
        }

Expected behavior

Catch type changing from collection to array here: IEnumerable<int> fib2 = fib.Where(x => x > 2).ToArray();.

Actual behavior

Catches type change here: Console.WriteLine($"{fib2[0]");.

[DustinCampbell]

I’m not sure what you might be nullify-er.

There are a couple of fixes I could imagine. Here’s a couple:

1. Use var to infer the type of fib2 as an int[]. After all, why does it need to be of type IEnumerable<int>?

var fib2 = fib.Where(x => x > 2).ToArray();
Console.WriteLine($"{ fib2[0] }");

1. Don’t call ToArray() at all.

var fib2 = fib.Where(x => x > 2);
Console.WriteLine($"{ fib2.First() }");

[DustinCampbell]

No problem!