例如，Lambda表达式使任务简单得多

var numbers = new List<int> { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 };

var oddNumbers = numbers.Where(x => x % 2 != 0);
var sumOfEven = numbers.Where(x => x % 2 == 0).Sum();

在上面的代码中，因为我们使用了lambda，所以我们在一行代码中得到奇数和偶数的和。

如果没有lambda，我们将不得不使用if/else或for循环。

因此，使用lambda来简化c#中的代码是很好的。

一些关于它的文章:

https://qawithexperts.com/article/c-sharp/lambda-expression-in-c-with-examples/470

https://exceptionnotfound.net/csharp-in-simple-terms-18-expressions-lambdas-and-delegates

http://dontcodetired.com/blog/post/Whats-New-in-C-10-Easier-Lambda-Expressions

很多时候，您只在一个地方使用功能，所以创建方法只会使类变得混乱。

Lambda清理了c# 2.0的匿名委托语法…例如

Strings.Find(s => s == "hello");

在c# 2.0中是这样完成的:

Strings.Find(delegate(String s) { return s == "hello"; });

在功能上，它们做的是完全相同的事情，只是语法更简洁。

Microsoft has given us a cleaner, more convenient way of creating anonymous delegates called Lambda expressions. However, there is not a lot of attention being paid to the expressions portion of this statement. Microsoft released a entire namespace, System.Linq.Expressions, which contains classes to create expression trees based on lambda expressions. Expression trees are made up of objects that represent logic. For example, x = y + z is an expression that might be part of an expression tree in .Net. Consider the following (simple) example:

using System;
using System.Linq;
using System.Linq.Expressions;


namespace ExpressionTreeThingy
{
    class Program
    {
        static void Main(string[] args)
        {
            Expression<Func<int, int>> expr = (x) => x + 1; //this is not a delegate, but an object
            var del = expr.Compile(); //compiles the object to a CLR delegate, at runtime
            Console.WriteLine(del(5)); //we are just invoking a delegate at this point
            Console.ReadKey();
        }
    }
}

This example is trivial. And I am sure you are thinking, "This is useless as I could have directly created the delegate instead of creating an expression and compiling it at runtime". And you would be right. But this provides the foundation for expression trees. There are a number of expressions available in the Expressions namespaces, and you can build your own. I think you can see that this might be useful when you don't know exactly what the algorithm should be at design or compile time. I saw an example somewhere for using this to write a scientific calculator. You could also use it for Bayesian systems, or for genetic programming (AI). A few times in my career I have had to write Excel-like functionality that allowed users to enter simple expressions (addition, subtrations, etc) to operate on available data. In pre-.Net 3.5 I have had to resort to some scripting language external to C#, or had to use the code-emitting functionality in reflection to create .Net code on the fly. Now I would use expression trees.

Lambda表达式对于匿名委托来说是一种更简单的语法，可以在任何可以使用匿名委托的地方使用。然而，反过来就不对了;lambda表达式可以转换为表达式树，这允许很多魔术，如LINQ到SQL。

下面是一个使用匿名委托的LINQ to Objects表达式的例子，然后是lambda表达式，以显示它们是多么容易。

// anonymous delegate
var evens = Enumerable
                .Range(1, 100)
                .Where(delegate(int x) { return (x % 2) == 0; })
                .ToList();

// lambda expression
var evens = Enumerable
                .Range(1, 100)
                .Where(x => (x % 2) == 0)
                .ToList();

Lambda表达式和匿名委托相对于编写单独的函数有一个优势:它们实现了闭包，允许您将局部状态传递给函数，而无需向函数添加参数或创建一次性对象。

表达式树是c# 3.0的一个非常强大的新特性，它允许API查看表达式的结构，而不仅仅是获取一个可以执行的方法的引用。API只需要将委托参数转换为Expression<T>参数，编译器就会从lambda而不是匿名委托生成表达式树:

void Example(Predicate<int> aDelegate);

被称为:

Example(x => x > 5);

就变成:

void Example(Expression<Predicate<int>> expressionTree);

后者将获得描述表达式x > 5的抽象语法树的表示。LINQ to SQL依赖于此行为，能够将c#表达式转换为服务器端过滤/排序等所需的SQL表达式。

这样可以避免在远离使用方法的地方定义只在特定位置使用一次的方法。好的用途是作为泛型算法(如排序)的比较器，然后您可以定义一个自定义排序函数，在该函数中调用排序，而不是进一步迫使您查看其他地方以查看您正在排序的对象。

这并不是真正的创新。LISP拥有lambda函数已经有30年或更长时间了。