Uh oh!
There was an error while loading. Please reload this page.
rustc::back::link: redo symbol mangling - #6956
Closed
Blei wants to merge 1 commit into
Closed
Conversation
Handle more characters that appear in types, most notably <>): were missing. Also the new scheme takes care that no two different input strings result in the same mangled string, which was not the case before. Fixes#6921
Blei
commented
Jun 5, 2013
ContributorAuthor
Hmm, that might be a good idea. Also, I'm not really sure if we handle the last case correctly (pushing all characters that are in XID Continue). Maybe this should be replaced by a warning instead. |
bors added a commit
that referenced
this pull request
Jun 5, 2013
Handle more characters that appear in types, most notably <>): were missing. Also the new scheme takes care that no two different input strings result in the same mangled string, which was not the case before. Fixes#6921
U007D pushed a commit
to U007D/rust-mos
that referenced
this pull request
Aug 21, 2026
7386: Handle box with allocator r=flodiebold a=tweksteen In 1.49.0, the definition of Box was modified to support an optional Allocator[1]. Adapt the parsing of the `box` keyword to supply the expected number of parameters to the constructor. [1] rust-lang@f288cd2Fixes: rust-lang#6956 Co-authored-by: Thiébaud Weksteen <tweek@google.com>
U007D pushed a commit
to U007D/rust-mos
that referenced
this pull request
Aug 21, 2026
7374: Add step to run analysis-stats on std r=lnicola a=tweksteen Run `analysis-stats` on `std` as part of the release workflow. Uses the `--with-deps` to also parse other crates defined in `stdlibs`. Remove the condition for exection, both analysis will be run for nightly and release builds. Do not submit until rust-lang#6956 has been fixed. Bug: rust-lang#6956 Co-authored-by: Thiébaud Weksteen <tweek@google.com>
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Handle more characters that appear in types, most notably <>): were
missing. Also the new scheme takes care that no two different input
strings result in the same mangled string, which was not the case before.
Fixes#6921