What exactly does a LINQ function return when there are no matches? Take the Where method, for example:
var numbers = Enumerable.Range(1, 10);
var results = numbers.Where(n => n == 50);
What would be in results at this point?
What exactly does a LINQ function return when there are no matches? Take the Where method, for example:
var numbers = Enumerable.Range(1, 10);
var results = numbers.Where(n => n == 50);
What would be in results at this point?
In this case it returns an IEnumerable<Int32>
with a count of 0 items.
results
itself is just a query. Until you start to iterate through it (either explicitly or via a call like Count()
), nothing has checked whether there are any results or not. It's only when you enumerate it that anything will happen.
So you could do:
foreach (int x in results)
{
Console.WriteLine("This won't happen");
}
Or:
Console.WriteLine(results.Any()); // Will print false
Console.WriteLine(results.Count()); // Will print 0
Any of these will cause the predicate to be evaluated against each item in the range... but before then, it won't be called at all.
This is an important thing to understand, because it means that results
couldn't be null
while retaining the feature of lazy evaluation - until you tried to use results
, it wouldn't have worked out whether it should be null
or not!