[lldb] Fix unsafe pointer type determination logic #8742
Merged
Conversation
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
|
This was affecting the ability to inspect swift-syntax values, where the design involves many generated types whose name begins with |
|
@swift-ci test |
adrian-prantl
approved these changes
May 10, 2024
augusto2112
approved these changes
May 11, 2024
kastiglione
deleted the
dl/lldb-Fix-unsafe-pointer-type-determination-logic
branch
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.
The synthetic provider for the Unsafe*Pointer types contains faulty logic that looks for the substring "Raw" in the fully populated type name, to determine if one of the
UnsafeRawpointer types should be used. In other words,UnsafeBufferPointer<MyTypeWithRawInTheName>will erroneously have theUnsafeRawBufferPointerformatter selected for it.rdar://127897493