Swift: Fix type string representation #19582
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
Contributor
There was a problem hiding this comment.
Pull Request Overview
Fixes the string representation of Swift TypeValueExpr by guarding the call to fetchLabel and passing both the syntax and resolved type when available.
- Added checks for
getParamTypeRepr()andgetParamType() - Updated
fetchLabelto accept both theTypeReprand theType - Removed the unconditional single-argument call
Comments suppressed due to low confidence (1)
swift/extractor/translators/ExprTranslator.cpp:694
- Add unit tests covering scenarios where
getParamTypeRepr()orgetParamType()is null to ensure the new conditional logic behaves as expected and avoids regressions.
if (expr.getParamTypeRepr() && expr.getParamType()) {
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.
No description provided.