Improve error messages when converting lambdas to expression trees#21380
Improve error messages when converting lambdas to expression trees#21380jcouv merged 4 commits intodotnet:masterfrom
Conversation
jcouv
left a comment
There was a problem hiding this comment.
LGTM
It looks like there previously was not test coverage for that error. Thanks!
|
@dotnet-bot test windows_release_unit32_prtest please |
|
master is currently targeting 15.5 which only accepts very severe bugs (at this point in the release cycle). I'll rebase this PR to post-15.5 branch. |
|
@dotnet-bot retest this please |
|
@svick It looks like master has drifted since the last time you refreshed this PR. I just want to give you a heads up that the bug bar is going to rise again for this milestone soon (around June 10th). I'll kick off new tests to get the current status. |
|
@dotnet-bot retest this please |
Also made minor fixes to previous test
07b55ee to
d87dd6a
Compare
|
@jcouv I have updated the PR. |
|
@AlekseyTs This community PR was rebased since you had reviewed. Can you take another look so we can merge? Thanks |
|
test windows_debug_unit32_prtest please |
|
@jaredpar Please approve for ask-mode for 15.8. Thanks |
|
approved |
|
Thanks @svick! |
Fixes #18645.
The first commit adds a failing test.
The second commit fixes it by changing reporting of CS1593 for expression trees from e.g.:
to:
The second commit also changes the wording of CS1661 from e.g.:
to:
FYI @tmat