Skip to content
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.

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

Expression trees can't represent some new C# syntax elements #18134

Closed
BillWagner opened this issue Apr 28, 2020 — with docs.microsoft.com · 3 comments
Closed

Expression trees can't represent some new C# syntax elements #18134

BillWagner opened this issue Apr 28, 2020 — with docs.microsoft.com · 3 comments
Labels
advanced-concepts/subsvc csharp-linq/subsvc doc-enhancement Improve the current content [org][type][category] dotnet-csharp/svc Pri2 won't fix Issues that were closed as part of automated backlog grooming

Comments

Copy link
Member

See #17988 (comment)

Some of the new language elements aren't translated into expression trees. The null forgiving operator ! is one. The null propagating operator ?. is another. I think pattern matching switch expressions are also affected.

We should update this section to include unsupported language elements, and guidance on general use.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@BillWagner BillWagner added 🗃️ Technology - C# Advanced concepts doc-enhancement Improve the current content [org][type][category] and removed ⌚ Not Triaged Not triaged labels Apr 29, 2020
@AntonLapounov
Copy link
Member

Expression trees have many restrictions, see all those Error() calls in https://github.com/dotnet/roslyn/blob/master/src/Compilers/CSharp/Portable/Lowering/DiagnosticsPass_ExpressionTrees.cs.

@Joe4evr
Copy link
Contributor

Joe4evr commented Jul 13, 2020

Related: dotnet/csharplang#158

@PRMerger6 PRMerger6 added the Pri2 label Jan 16, 2021
@dotnet-bot dotnet-bot added the won't fix Issues that were closed as part of automated backlog grooming label Jan 25, 2021
@dotnet-bot
Copy link
Contributor

This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
advanced-concepts/subsvc csharp-linq/subsvc doc-enhancement Improve the current content [org][type][category] dotnet-csharp/svc Pri2 won't fix Issues that were closed as part of automated backlog grooming
Projects
None yet
Development

No branches or pull requests

6 participants