Expressions vs Lambdas

I know what a Lambda Expression is.

But I am not sure if that is the same thing as an Expr开发者_StackOverflow社区ession. There seems to be more to know here than I know.

I am looking at wrapping IQueryable and that uses Expressions a lot. So, for example, is there more to the 'Expression' parameter here than can be thought of in a Lambda?

public InterceptedQuery(InterceptingProvider provider, Expression expression) 
{ 
    this._provider = provider; 
    this._expression = expression; 
}  

A lambda expression is a compiler feature that is compiled, depending on context, into one of two things:

• A (hidden) function and a delegate to it
• An Expression

Once the application has been compiled, the concept of a lambda expression doesn't exist, as it's been turned into one of the above two options.

I'm not sure what you mean by

is there more to the 'Expression' parameter here than can be thought of in a Lambda

An expression encapsulates and expressed application logic in an inspectable form (in other words, it lets you see what the developer wrote in terms of properties and functions invoked, constants included, comparisons, etc.). This is how query providers (for the most part, object-relational mappers like the Entity Framework) take code and turn it into SQL.

Lambdas are generally compiled code, where Expression represents "abstract syntax trees" (AST), ie. a data structure that represents code, and can be compiled to code. IQueryable generally operates on Expression because it's supposed to compile the AST to code that runs in different environments, like an SQL server, instead of just the host machine. There are IQueryableProviders that compile to SQL (Linq2Sql), to JavaScript, to OpenGL shaders (Bling), and more.

The C# compiler can sometimes turn a lambda into an expression, if the method parameter expects an expression of the right type:

void Foo(Expression<Func<int>>) { ... }
...
Foo(() => 3);