I strongly doubt it. It's only mimicking the IEnumerable<T> bits of LINQ; there's nothing like IQueryable<T> in there. I think that one thing a lot of people a

I strongly doubt it. It's only mimicking the IEnumerable<T> bits of LINQ; there's nothing like IQueryable<T> in there. I think that one thing a lot of people are missing when they talk about the Expressions bit of LINQ is that LINQ is really two different things that have two different killer features. There's the set of extensions on top of IEnumerable<T>, which are mostly used for writing declarative replacements for for-loops, and also supporting things like PLINQ. As far as I'm aware, IEnumerable<T>'s MSDN documentation doesn't even mention expression trees. And there's the (much more complicated) IQueryable<T> interface, which is the bit that supports things like the LINQ interface to Entity Framework, and is all about expression trees. The IEnumerable<T> bits aren't as fancy, but they are still quite useful.