Skip to content

Update lambda expression documentation to clarify method call behavior in expression trees #47037

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 2, 2025
Merged

Update lambda expression documentation to clarify method call behavior in expression trees #47037

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ef6e4ed
Initial plan
Copilot Jun 30, 2025
5acde11
Update lambda expression documentation to clarify method call behavio…
Copilot Jun 30, 2025
55c7a0e
Update docs/csharp/language-reference/operators/lambda-expressions.md
BillWagner Jul 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/csharp/language-reference/operators/lambda-expressions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ A lambda expression with an expression on the right side of the `=>` operator is
(input-parameters) => expression
```

The body of an expression lambda can consist of a method call. However, when creating [expression trees](../../advanced-topics/expression-trees/index.md) evaluated by a query provider, limit method calls to those methods recognized by the query provider. Otherwise, the query provider can't replicate the method's function.
The body of an expression lambda can consist of a method call. However, when creating [expression trees](../../advanced-topics/expression-trees/index.md) evaluated by a query provider, you should limit method calls to those methods that the query provider translates to its format. Different query providers have varying capabilities—for example, many SQL-based providers can translate methods like <xref:System.String.StartsWith%2A?displayProperty=nameWithType> into appropriate SQL expressions such as `LIKE`. If a query provider doesn't recognize a method call, it can't translate or execute the expression.

## Statement lambdas

Expand Down