I just looked at one of those libraries that has a something-linq naming scheme, expecting to get more knowledge on how to build expression trees in an elegant way - and was disappointed. Because all I could find were methods that extended IEnumerable - of course, with "normal" C # code.
Now I have this question: are the expressions for the expression for IEnumerable not really decrypting the library name in order to have "Linq" in it? Or is the author just jumping into the hype trying to get more downloads for his IEnumerable extension library, and I was right in expecting IQueryable and expressions when looking at "Linq" in the name of the library?
Edit:
I would say that there is a difference between the Linq-to -... and something-Linq libraries. IMHO Linq-to -... are linq provider libraries, something-Linq are linq extensions. I think that the Linq vendor libraries can choose whether they will expose IQueryable or IEnumerable in their results - linq extensions have no such choice. As far as I know, they should be able to work with both vendor libraries. For me, this means that all linq extensions must contain both Queryable and Enumerable extensions.
Edit 2:
In the commentary on his answer, a very lively discussion took place between me and me. I volunteered to create a blogpost to hopefully clarify the situation:
LINQ Uncharted Mapping
Edit 3:
, , . , - .