[release/dev18.9] Optimizer: fix accessing captured values when skipping inlining - #20331
Merged
Merged
Conversation
The DebugInlineAsCall 'SRTP 31 - Capture used in nested closure' baseline differs from the committed one only in the emission order of the Test::<g>__debug@5 method block on release/dev18.9; all IL is byte-identical. Program still compiles and runs correctly (compileAndRun returns 0). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
T-Gro
enabled auto-merge (squash)
August 24, 2026 11:01
abonie
approved these changes
Aug 24, 2026
T-Gro
disabled auto-merge
August 24, 2026 11:20
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
3 participants
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.
Backport of #20089 to release/dev18.9
/cc @T-Gro @auduchinok
Note: Release notes and
eng/commonfiles are excluded from this backport. If release notes are needed, they should be added manually to the appropriate version file for this branch.Customer Impact
Testing
Risk
IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.