tests: Ensure malformed symbol remains invalid - #505
Merged
Conversation
haberman
approved these changes
Aug 27, 2026
Collaborator
Author
|
Failed checks for Windows CI seem to be due to an issue with using windows-latest as the runner, instead of an issue with this pull request. Opened #506 to follow up |
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
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.
Newer versions of the Swift demangler return true on
isSwiftSymbol("_TMXfZD")due to_Tbeing a real legacy prefix for Swift mangling. This change updates the symbol name to ensure that it is invalid, and is not accidentally parsed by the Swift demangler.