When to use lambda expressions instead of a Where clause in LINQ

Question

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. Primari

Answer 1

Read this. Your LINQ queries will get turned into Lambda expressions by the compiler at run time.

Answer 2

http://theburningmonk.com/2010/02/linq-lambda-expression-vs-query-expression/

Answer 3

Take a look at this article: LINQ Query Syntax versus Method Syntax :

In general, we recommend query syntax because it is usually simpler and more readable; however there is no semantic difference between method syntax and query syntax. In addition, some queries, such as those that retrieve the number of elements that match a specified condition, or that retrieve the element that has the maximum value in a source sequence, can only be expressed as method calls. The reference documentation for the standard query operators in the System.Linq namespace generally uses method syntax. Therefore, even when getting started writing LINQ queries, it is useful to be familiar with how to use method syntax in queries and in query expressions themselves.

And also this question: LINQ: Dot Notation vs Query Expression

Answer 4

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.