Handle unsized consts with type str in v0 symbol mangling - #130344
Merged
Merged
Conversation
BoxyUwU
reviewed
Sep 16, 2024
BoxyUwU
reviewed
Sep 19, 2024
commented
Sep 19, 2024
Member
|
Can you also squash all of your commits into one? I think this is good to merge afterwards :) |
This comment has been minimized.
This comment has been minimized.
commented
Sep 22, 2024
Member
|
@bors r+ rollup thank you for the PR :) |
commented
Sep 22, 2024
This was referenced Sep 23, 2024
ghost
deleted the
fix-116306
branch
September 26, 2024 12: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
5 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.
This PR fixes #116303 by handling consts with type
strin v0 symbol mangling as partial support for unsized consts.This PR is related to
# and#.r? @BoxyUwU