IEnumerable describes behavior, while List is an implementation of that behavior. When you use IEnumerable, you give the compiler a chance to defer work until later, possibly optimizing along the way. If you use ToList() you force the compiler to reify the results right away.
Whenever I’m “stacking” LINQ expressions, I use IEnumerable, because by only specifying the behavior I give LINQ a chance to defer evaluation and possibly optimize the program. Remember how LINQ doesn’t generate the SQL to query the database until you enumerate it? Consider this:
public IEnumerable
{
return from a in Zoo.Animals
where a.coat.HasSpots == true
select a;
}
public IEnumerable
{
return from a in sample
where a.race.Family == “Felidae”
select a;
}
public IEnumerable
{
return from a in sample
where a.race.Family == “Canidae”
select a;
}
Now you have a method that selects an initial sample (“AllSpotted”), plus some filters. So now you can do this:
var Leopards = Feline(AllSpotted());
var Hyenas = Canine(AllSpotted());
So is it faster to use List over IEnumerable? Only if you want to prevent a query from being executed more than once. But is it better overall? Well in the above, Leopards and Hyenas get converted into single SQL queries each, and the database only returns the rows that are relevant. But if we had returned a List from AllSpotted(), then it may run slower because the database could return far more data than is actually needed, and we waste cycles doing the filtering in the client.
In a program, it may be better to defer converting your query to a list until the very end, so if I’m going to enumerate through Leopards and Hyenas more than once, I’d do this:
List
List
There is a very good article written by: Claudio Bernasconi’s TechBlog here: When to use IEnumerable, ICollection, IList and List
Here some basics points about scenarios and functions: