Demangle an OpaqueArchetypeTypeRef's ID as a type not as a symbol #63508
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.
(cherry picked from commit e2febea)
rdar://104982758
Cherry-pick of https://github.com/apple/swift/pull/61091
Fix a bug which would crash the demangler when trying to process opaque types when used from remote mirrors.
For example, when debugging the following code in LLDB:
The demangler will crash when trying to demangle the type of
t
without this changeMain Branch PR: Demangle an OpaqueArchetypeTypeRef's ID as a type not as a symbol #62043
Resolves: rdar://104982758
Risk: Low. This has been merged in the main branch since December 21st with no problems. Also, only LLDB or other remote mirrors users should exercise this code path.
Testing: LLDB test case added in [lldb] Add TestBoundOpaqueArchetype test llvm-project#5848.