LinqVsLambda.txt ---------- 20190811 linq vs lambda linq = Language Integrated Query Visual Studio 提供(能以類似 SQL 語法查詢)的功能. 例: (較具可讀性) var _Results = from item in _List where item.Value == 1 select item; lambda = an anonymous function and is more of a like delegate type. 代表一個匿名函數, 比較像一個 delegate. 運算式中有一個 "=>" 運算符號, 讀為 "goes to". 運算式左邊為輸入的參數. 例: (較簡潔, 可用一行指令就完成) var _Results = _List.Where(x => x.Value == 1); ref: https://social.msdn.microsoft.com/Forums/sqlserver/zh-TW/15948827-3163-48d0-b591-8654ad86d444/linq-vs-lambda?forum=csharpgeneral Adding with Kristin's answer, There is no difference in performance because after compile they generate same IL code for the same query. Language Integrated Query (LINQ) is feature of Visual Studio that gives you the capabilities yo query on the language syntax of C#, so you will get SQL kind of queries. And Lambda expression is an anonymous function and is more of a like delegate type. All lambda expressions use the lambda operator =>, which is read as "goes to". lambda 運算式都使用 "=>" 符號, 並讀為 "goes to". The left side of the lambda operator specifies the input parameters (if any) and the right side holds the expression or statement block. Personally I like Lambda Expression. Hope this helps you. Here is an MSDN article for your question which can explain it in more detail for your better understanding: Query Syntax and Method Syntax Generally the lambda you are referring to is considered method syntax. Whereas query syntax looks more like a SQL query. They are both LINQ and performance will be identical, as the compiler will turn any query syntax into method syntax under the hood. 使用 Lambda 代表呼叫一個匿名函數. 其中的查詢語法有點像 SQL 查詢. 編譯器會把 Lambda 運算式編譯為 匿名函數 後再執行, 因此使用 Lambda 跟 呼叫匿名函數, 兩者的執行效能是一樣的, 但是 Lambda 可以簡略的語法, 取代複雜的匿名函數撰寫過程. There are scenarios when lambda can be used for anonymous methods and isn't considered LINQ: Lambda Expressions C# Back to your question, generally when making the decision vs query and method, my personal preference is to use method syntax because it can usually be done in one line. If it is a complex LINQ query it may be easier to read using query syntax. My colleagues and I have different personal preferences, but always tend to use what is easier to read depending on the query. 有些情況適合以 Lambda 取代匿名函數, 但是不適合 使用 LINQ. 重點是維持可讀性. This is LINQ (using query syntax): 使用 LINQ 查詢語法: var _Results = from item in _List where item.Value == 1 select item; This is using Lambdas. 使用 Lambdas: var _Results = _List.Where(x => x.Value == 1); The second one is using Lambdas. Lambda Expressions could be more complex in this scenario. At least, the LINQ query with LINQ operators is easier to understand. But in most cases, LINQ operator and Lambda Expressions are both fine to me. Their termination are both calling LINQ extension methods, the difference is what the compiler does for us. 以上例子兩者執行效能均同, 編譯器會幫我們編譯為匿名函數後再執行. LINQ 較具可讀性. Lambda 可用一行指令就完成. Lambdas are the inline method type things that you are passing as a parameter to the Where function in the second example. >>any running performance difference between linq and lambda? As far as I know, there is no, Linq is based on Lambda. They should work the same for any given query though of course the compiler may choose a slightly different interpretation of a complicated linq query. ---------- 20190808 int[] ia1 = { 1, 3, 5, 7, 9 }; int iCount = (from number in ia1 where number > 5 select number).Count(); // 2 int iSum = (from number in ia1 where number > 5 select number).Sum(); // 16 ---------- 20190123 ref: https://jax-work-archive.blogspot.com/2014/02/c-sharp-delegate-to-lambda-expressions-syntax-transform.html 一開始要看懂 Lambda Expressions 有點困難，下面會以演進方式來介紹如何做到語法省略。 首先定義一個單參數的 delegate delegate int Del(int x); 以傳統 delegate 的語法來建構 delegate Del a = delegate(int x) { return x + 2; }; 去掉 delegate 改成 Lambda 表示式 Del a = (int x) => { return x + 2; }; 由於大括號裡只有一句陳述式，而且是一個 return 的陳述式,所以可以省略大括號跟 return Del a = (int x) => x + 2; 在 delegate 已經有定義輸入參數的型別，所以在小括號裡的型別可以省略 Del a = (x) => x + 2; 由於小括號裡面只有一個輸入參數，所以可以再進一步省略小括號 Del a = x => x + 2; 使用例: int? a = (new List{2}).Select(x => x).FirstOrDefault(); // 2 int? b = (new List{}).Select(x => x).FirstOrDefault(); // 0 int? c = (new List{2}).Select(x => (int?)x).FirstOrDefault(); // 2 int? d = (new List{}).Select(x => (int?)x).FirstOrDefault(); // null ---------- 20190123 ref: https://docs.microsoft.com/zh-tw/dotnet/csharp/programming-guide/statements-expressions-operators/lambda-expressions Lambda 運算式是 匿名函式 ，可用來建立 委派 或 運算式樹狀架構 類型 使用 Lambda 運算式可以撰寫區域函式，這些函式可以當做引數傳遞，或是當做函式呼叫的值傳回。 Lambda 運算式對於撰寫 LINQ 查詢運算式而言特別有用。 (input-parameters) => expression 兩個或多個輸入參數會包含在括號中，並且以逗號分隔: (x, y) => x == y 指定類型: (int x, string s) => s.Length > x 以空括號指定零個輸入參數: () => SomeMethod() 陳述式 Lambda 看起來就像是運算式 Lambda，不同之處在於，陳述式會包含於大括號內： (input-parameters) => { statement; } 陳述式 Lambda 的主體可以包含任意數目的陳述式，但是實際上通常不會超過兩個或三個陳述式。 delegate void TestDelegate(string s); TestDelegate del = n => { string s = n + " World"; Console.WriteLine(s); }; ---------- Lambda Expression 匿名方法的簡潔寫法 ref: https://jeffprogrammer.wordpress.com/2016/01/02/觀念-lambda-expression-func/ Lambda Expression 是傳統匿名方法的簡潔寫法，許多高階程式語言都支援，例如 Java 、 C++ 、 C# 等。 C# Lambda Expression 使用 「 => 」 做為運算符號，讀法很多種，像是 「such that」、「maps to」、「lambda」、「goes to 」。 語法如下所示： ( 參數 ) => { 運算式 } 這語法做的事是：把左邊的參數丟到右邊的運算式去做運算。 Lambda Expression 經常用在委派 ( delegate ) 。 我們看下面的例子。 上圖程式的 list.FindAll( )需要輸入的參數是委派方法 Predicate。 傳統寫法是自己去定義一個方法來被委派。 較簡單的寫法是匿名，如上圖的這段： delegate(int i) { return (i % 2) == 0; } Lambda Expression 提供一個更簡潔的寫法： i => ( i % 2 ) == 0 ---------- 20181221 原本的 Func 匿名方法委派方式: using System; public class Anonymous { public static void Main() { Func convert = delegate(string s) { return s.ToUpper();}; string name = "Dakota"; Console.WriteLine(convert(name)); } } 相同的Func 改用 Lambda運算式委派Func: using System; public class LambdaExpression { public static void Main() { Func convert = s => s.ToUpper(); string name = "Dakota"; Console.WriteLine(convert(name)); } } ---------- 20181109 以下兩者意義相同: 1. timer.Elapsed += async ( sender, e ) => await HandleTimer(); private Task HandleTimer() { Console.WriteLine("\nHandler not implemented..." ); return Task.FromResult(null); } 2. timer.Elapsed = CallHandleTimer; async void CallHandleTimer(object sender, EventArgs e) { await HandleTimer(); } 以下兩者意義相同: 1. using System; using System.Threading; using System.Threading.Tasks; public class Example { public static void Main() { ShowThreadInfo("Application"); var t = Task.Run(() => ShowThreadInfo("Task") ); t.Wait(); } static void ShowThreadInfo(String s) { Console.WriteLine("{0} Thread ID: {1}", s, Thread.CurrentThread.ManagedThreadId); } } // The example displays the following output: // Application thread ID: 1 // Task thread ID: 3 2. using System; using System.Threading; using System.Threading.Tasks; public class Example { public static void Main() { Console.WriteLine("Application thread ID: {0}", Thread.CurrentThread.ManagedThreadId); var t = Task.Run(() => { Console.WriteLine("Task thread ID: {0}", Thread.CurrentThread.ManagedThreadId); } ); t.Wait(); } } // The example displays the following output: // Application thread ID: 1 // Task thread ID: 3 ---------- 20180928 Lambda Expressions ref: https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/statements-expressions-operators/lambda-expressions https://docs.microsoft.com/zh-tw/dotnet/csharp/programming-guide/statements-expressions-operators/lambda-expressions In this article Expression Lambdas Statement Lambdas Async Lambdas Lambdas with the Standard Query Operators Type Inference in Lambdas Variable Scope in Lambda Expressions C# Language Specification Featured Book Chapter See Also A lambda expression is an anonymous function that you can use to create delegates or expression tree types. By using lambda expressions, you can write local functions that can be passed as arguments or returned as the value of function calls. Lambda expressions are particularly helpful for writing LINQ query expressions. To create a lambda expression, you specify input parameters (if any) on the left side of the lambda operator =>, and you put the expression or statement block on the other side. For example, the lambda expression x => x * x specifies a parameter that’s named x and returns the value of x squared. You can assign this expression to a delegate type, as the following example shows: 原先使用 delegate 的語法, 可利用 lambda expression 簡化語法如下: delegate int del(int i); static void Main(string[] args) { del myDelegate = x => x * x; int j = myDelegate(5); //j = 25 } To create an expression tree type: using System.Linq.Expressions; namespace ConsoleApplication1 { class Program { static void Main(string[] args) { Expression myET = x => x * x; } } } The => operator has the same precedence as assignment (=) and is right associative (see "Associativity" section of the Operators article). Lambdas are used in method-based LINQ queries as arguments to standard query operator methods such as Where. When you use method-based syntax to call the Where method in the Enumerable class (as you do in LINQ to Objects and LINQ to XML) the parameter is a delegate type System.Func. A lambda expression is the most convenient way to create that delegate. When you call the same method in, for example, the System.Linq.Queryable class (as you do in LINQ to SQL) then the parameter type is an System.Linq.Expressions.Expression where Func is any of the Func delegates with up to sixteen input parameters. Again, a lambda expression is just a very concise way to construct that expression tree. The lambdas allow the Where calls to look similar although in fact the type of object created from the lambda is different. In the previous example, notice that the delegate signature has one implicitly-typed input parameter of type int, and returns an int. The lambda expression can be converted to a delegate of that type because it also has one input parameter (x) and a return value that the compiler can implicitly convert to type int. (Type inference is discussed in more detail in the following sections.) When the delegate is invoked by using an input parameter of 5, it returns a result of 25. Lambdas are not allowed on the left side of the is or as operator. All restrictions that apply to anonymous methods also apply to lambda expressions. For more information, see Anonymous Methods. ---------- Expression Lambdas A lambda expression with an expression on the right side of the => operator is called an expression lambda. Expression lambdas are used extensively in the construction of Expression Trees. An expression lambda returns the result of the expression and takes the following basic form: (input-parameters) => expression The parentheses are optional only if the lambda has one input parameter; otherwise they are required. Two or more input parameters are separated by commas enclosed in parentheses: (x, y) => x == y Sometimes it is difficult or impossible for the compiler to infer the input types. When this occurs, you can specify the types explicitly as shown in the following example: (int x, string s) => s.Length > x Input paramater types must be all explicit or all implicit; otherwise, C# generates a CS0748 compiler error. Specify zero input parameters with empty parentheses: () => SomeMethod() Note in the previous example that the body of an expression lambda can consist of a method call. However, if you are creating expression trees that are evaluated outside of the .NET Framework, such as in SQL Server, you should not use method calls in lambda expressions. The methods will have no meaning outside the context of the .NET common language runtime. ---------- Statement Lambdas A statement lambda resembles an expression lambda except that the statement(s) is enclosed in braces: (input-parameters) => { statement; } The body of a statement lambda can consist of any number of statements; however, in practice there are typically no more than two or three. delegate void TestDelegate(string s); TestDelegate del = n => { string s = n + " World"; Console.WriteLine(s); }; Statement lambdas, like anonymous methods, cannot be used to create expression trees. ---------- Async Lambdas You can easily create lambda expressions and statements that incorporate asynchronous processing by using the async and await keywords. For example, the following Windows Forms example contains an event handler that calls and awaits an async method, ExampleMethodAsync. public partial class Form1 : Form { public Form1() { InitializeComponent(); } private async void button1_Click(object sender, EventArgs e) { // ExampleMethodAsync returns a Task. await ExampleMethodAsync(); textBox1.Text += "\r\nControl returned to Click event handler.\n"; } async Task ExampleMethodAsync() { // The following line simulates a task-returning asynchronous process. await Task.Delay(1000); } } You can add the same event handler by using an async lambda. To add this handler, add an async modifier before the lambda parameter list, as the following example shows. public partial class Form1 : Form { public Form1() { InitializeComponent(); button1.Click += async (sender, e) => { // ExampleMethodAsync returns a Task. await ExampleMethodAsync(); textBox1.Text += "\nControl returned to Click event handler.\n"; }; } async Task ExampleMethodAsync() { // The following line simulates a task-returning asynchronous process. await Task.Delay(1000); } } For more information about how to create and use async methods, see Asynchronous Programming with async and await. ---------- Lambdas with the Standard Query Operators Many Standard query operators have an input parameter whose type is one of the Func family of generic delegates. These delegates use type parameters to define the number and types of input parameters, and the return type of the delegate. Func delegates are very useful for encapsulating user-defined expressions that are applied to each element in a set of source data. For example, consider the following delegate type: public delegate TResult Func(TArg0 arg0) The delegate can be instantiated as Func myFunc where int is an input parameter and bool is the return value. The return value is always specified in the last type parameter. Func defines a delegate with two input parameters, int and string, and a return type of bool. The following Func delegate, when it is invoked, will return true or false to indicate whether the input parameter is equal to 5: Func myFunc = x => x == 5; bool result = myFunc(4); // returns false of course You can also supply a lambda expression when the argument type is an Expression, for example in the standard query operators that are defined in System.Linq.Queryable. When you specify an Expression argument, the lambda will be compiled to an expression tree. A standard query operator, the Count method, is shown here: int[] numbers = { 5, 4, 1, 3, 9, 8, 6, 7, 2, 0 }; int oddNumbers = numbers.Count(n => n % 2 == 1); The compiler can infer the type of the input parameter, or you can also specify it explicitly. This particular lambda expression counts those integers (n) which when divided by two have a remainder of 1. The following line of code produces a sequence that contains all elements in the numbers array that are to the left side of the 9 because that's the first number in the sequence that doesn't meet the condition: var firstNumbersLessThan6 = numbers.TakeWhile(n => n < 6); This example shows how to specify multiple input parameters by enclosing them in parentheses. The method returns all the elements in the numbers array until a number is encountered whose value is less than its position. Do not confuse the lambda operator (=>) with the greater than or equal operator (>=). var firstSmallNumbers = numbers.TakeWhile((n, index) => n >= index); ---------- Type Inference in Lambdas When writing lambdas, you often do not have to specify a type for the input parameters because the compiler can infer the type based on the lambda body, the parameter’s delegate type, and other factors as described in the C# Language Specification. For most of the standard query operators, the first input is the type of the elements in the source sequence. So if you are querying an IEnumerable, then the input variable is inferred to be a Customer object, which means you have access to its methods and properties: customers.Where(c => c.City == "London"); The general rules for lambdas are as follows: 1. The lambda must contain the same number of parameters as the delegate type. 2. Each input parameter in the lambda must be implicitly convertible to its corresponding delegate parameter. 3. The return value of the lambda (if any) must be implicitly convertible to the delegate's return type. Note that lambda expressions in themselves do not have a type because the common type system has no intrinsic concept of "lambda expression." However, it is sometimes convenient to speak informally of the "type" of a lambda expression. In these cases the type refers to the delegate type or Expression type to which the lambda expression is converted. ---------- Variable Scope in Lambda Expressions Lambdas can refer to outer variables (see Anonymous Methods) that are in scope in the method that defines the lambda function, or in scope in the type that contains the lambda expression. Variables that are captured in this manner are stored for use in the lambda expression even if the variables would otherwise go out of scope and be garbage collected. An outer variable must be definitely assigned before it can be consumed in a lambda expression. The following example demonstrates these rules: delegate bool D(); delegate bool D2(int i); class Test { D del; D2 del2; public void TestMethod(int input) { int j = 0; // Initialize the delegates with lambda expressions. // Note access to 2 outer variables. // del will be invoked within this method. del = () => { j = 10; return j > input; }; // del2 will be invoked after TestMethod goes out of scope. del2 = (x) => {return x == j; }; // Demonstrate value of j: // Output: j = 0 // The delegate has not been invoked yet. Console.WriteLine("j = {0}", j); // Invoke the delegate. bool boolResult = del(); // Output: j = 10 b = True Console.WriteLine("j = {0}. b = {1}", j, boolResult); } static void Main() { Test test = new Test(); test.TestMethod(5); // Prove that del2 still has a copy of // local variable j from TestMethod. bool result = test.del2(10); // Output: True Console.WriteLine(result); Console.ReadKey(); } } The following rules apply to variable scope in lambda expressions: 1. A variable that is captured will not be garbage-collected until the delegate that references it becomes eligible for garbage collection. 2. Variables introduced within a lambda expression are not visible in the outer method. 3. A lambda expression cannot directly capture an in, ref, or out parameter from an enclosing method. 4. A return statement in a lambda expression does not cause the enclosing method to return. 5. A lambda expression cannot contain a goto statement, break statement, or continue statement that is inside the lambda function if the jump statement’s target is outside the block. It is also an error to have a jump statement outside the lambda function block if the target is inside the block. ---------- 20160228 before 「Lambda 運算式」(Lambda Expression) 是一種匿名函式，它可以包含運算式和陳述式 (Statement)，而且可以用來建立委派 (Delegate) 或運算式樹狀架構型別。 所有的 Lambda 運算式都會使用 Lambda 運算子 =>，意思為「移至」。Lambda 運算子的左邊會指定輸入參數 (如果存在)，右邊則包含運算式或陳述式區塊。Lambda 運算式 x => x * x 的意思是「x 移至 x 乘以 x」。這個運算式可以指派成委派型別 (Delegate Type)，如下所示： delegate int del(int i); del myDelegate = x => x * x; int j = myDelegate(5); //j = 25 ---------- using System; using System.Linq; public class CSharpLab { //宣告一個delegate, 自訂a, b二數運算的邏輯 delegate int myLogic(int a, int b); public static void Test() { int x=3, y=5; //原本的標準delegate寫法, 要額外宣告一個Method calc(x, y, new myLogic(addMethod)); //省事一點的匿名寫法 calc(x, y, delegate(int a, int b) { return a+b; }); //再省下去，就來段黏巴達(Lambada)Lambda吧 calc(x, y, (a,b)=>a+b); calc(x, y, (a,b)=>a-b); calc(x, y, (a,b)=>a*b); } static void calc(int x, int y, myLogic cc) { Console.WriteLine(cc(x, y)); } static int addMethod(int a, int b) { return a+b; } } ----------