Fix evaluations inside ref-returning methods#83037
Merged
AlekseyTs merged 1 commit intodotnet:mainfrom Apr 3, 2026
Merged
Conversation
Contributor
Author
|
@dotnet/roslyn-compiler for review |
RikkiGibson
approved these changes
Apr 2, 2026
Member
|
Would probably be good for @tmat and @AlekseyTs to review if possible |
Contributor
|
@asundheimMSFT Thank you for the contribution |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
After investigating this issue: https://developercommunity.visualstudio.com/t/Conditional-breakpoint-is-not-respecting/11063626
I determined that for evaluations inside
ref-returning frames, the expression compiler would generate query method signatures indicating that the return type isT&(ref T), while the query method itself still returnedT(as expected).In particular, this bug breaks breakpoint conditions in VS; typical conditions rely on comparisons, which return
Int32and the debugger can make the implicit conversion fromInt32to the method signatureboolreturn type. Inref-returning methods, the debugger cannot make the implicit conversion when the signature indicatesbool&.Details
Clearly this is an oversight on the C# expression compiler side; the VB EE already handles this correctly (EEMethodSymbol.vb)
The change is to make
EEMethodSymbolnot inheritRefKindand instead returnRefKind.None.Testing
Added unit test; deployed changes to experimental instance and verified the linked original issue is fixed.
Microsoft Reviewers: Open in CodeFlow