14 ms·
LINQ is best when used on in-memory object graphs, partly for the reasons you brought up, and partly because then you're not dealing with weird limitations or d
by int_19h 5y ago
LINQ is best when used on in-memory object graphs, partly for the reasons you brought up, and partly because then you're not dealing with weird limitations or deviations from how functions normally work etc. For in-memory queries, it's basically just a very advanced form of sequence comprehensions.
(I also suspect that the vast majority of LINQ code in the wild is of that variety, rather than Entity Framework etc.)