[REG2.065a] Issue 11718 - Unintended mangled names conflict of nested template structs #2953
Conversation
This file contains 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
…e structs If a symbol has parent, the parent part of the mangled name should also be unique in each scopes. Function symbols can have same identifiers in scope, so their parameters part must be always encoded in their mangled name to distinguish overloads. When I fixed bug 9271, I had naturally expected that behavior. However sadly `mangle` function had had a bug.
|
Auto-merge toggled on |
WalterBright
added a commit
that referenced
this pull request
Dec 16, 2013
[REG2.065a] Issue 11718 - Unintended mangled names conflict of nested template structs
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.
https://d.puremagic.com/issues/show_bug.cgi?id=11718
If a symbol has parent, the parent part of the mangled name should also be unique in each scopes.
Function symbols can have same identifiers in scope, so their parameters part must be always encoded in their mangled name to distinguish overloads.
When I fixed bug 9271 in #2877, I had naturally expected that behavior. However sadly
manglefunction had had a bug.