Fix ParseGenericTypeArgumentNames for nested generic types#1414
Merged
max-charlamb merged 1 commit intomicrosoft:mainfrom Apr 3, 2026
Merged
Conversation
ParseGenericTypeArgumentNames used IndexOf('<') to find the start of
generic arguments, which returns the first '<' in the full type name.
For nested generic types like Outer<A>+Inner<B>, this incorrectly
extracts the outer type's arguments (A) instead of the inner type's (B).
This breaks __Canon type resolution for AsyncStateMachineBox<TStateMachine>
because GetConcreteGenericTypeArguments resolves AsyncTaskMethodBuilder's
TResult instead of the state machine type, leaving the StateMachine field
with a null or wrong type after metadata fallback.
Fix: find the last '+' at depth 0 (outside angle brackets) to skip past
outer type names, then search for '<' from there.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
leculver
approved these changes
Apr 3, 2026
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.
GetConcreteGenericTypeArgumentswas resolvingVoidTaskResult(fromAsyncTaskMethodBuilder) instead of the state machine type, leaving theStateMachinefield with a null or wrong type after metadata fallback. This caused SOSDumpAsyncto crash with an assertion failure.Fix
Find the last
+at depth 0 (outside angle brackets) to skip past outer type names, then search for<from there.Verification
AsyncTaskMethodBuilder<VoidTaskResult>+AsyncStateMachineBox<MyClass+<DoAsync>d__3>VoidTaskResult❌MyClass+<DoAsync>d__3✅Dictionary<String, Int32>String, Int32✅String, Int32✅Dictionary<String, Int32>+EntryString, Int32❌Fixes the regression reported in dotnet/diagnostics#5789.