I've been really digging into LINQ, and I'm trying to hash out this lambda expression business. I'm just not seeing the benefit of some of the nuances of the syntax. Primarily, it seems to me that a lambda expression is mostly just a different way of using a Where clause. Why wouldn't I just use a Where clause then? Is the lambda expression more efficient?
Is it just another syntactical addition to draw programmers from another group to feel more comfortable in C#? Are there other better use cases for lambda expressions that I just haven't exposed to yet?
Internally, the compiler will translate the query syntax into the more explicit lambda syntax. There is no inherent performance gain for either style and the generated code for most scenarios is almost identical to what people type out by hand.
The main difference is that with the lambda syntax you can chain in any extension method operating off and returning and
IEnumerable<T>
. With the query syntax, you are limited to the particular extension methods explicitly supported by the language (varies between language)Really using or not using the query syntax is really a matter of personal preference.
Take a look at this article: LINQ Query Syntax versus Method Syntax :
And also this question: LINQ: Dot Notation vs Query Expression
Read this. Your LINQ queries will get turned into Lambda expressions by the compiler at run time.
http://theburningmonk.com/2010/02/linq-lambda-expression-vs-query-expression/