This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

System.Collections.IEnumerable subset =

from i in numbers where i < 10 select i;

While this is syntactically correct, implicit typing cleans things up considerably when working

with LINQ queries:

static void QueryOverInts()

{

int[] numbers = {10, 20, 30, 40, 1, 2, 3, 8};

// Use implicit typing here...

var subset = from i in numbers where i < 10 select i;

// ...and here.

foreach (var i in subset)

Console.WriteLine("Item: {0} ", i);

ReflectOverQueryResults(subset);

}

Recall that the var keyword should not be confused with the legacy COM Variant or loosely

typed variable declaration found in many scripting languages. The underlying type is determined

by the compiler based on the result of the initial assignment. After that point, it is a compiler error

to attempt to change the “type of type.” Furthermore, given the fact that in many cases the under-

lying type is the result of a dynamically generated anonymous type, it is commonplace to use

implicit typing whenever you wish to capture a LINQ result set.