Skip to content

[🍒 swift/release/6.2] Fix issue where target.source-map didn't apply to SwiftASTContext::Create #10529

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

DavidGoldman
Copy link

@DavidGoldman DavidGoldman commented Apr 23, 2025

This specifically is for SwiftASTContext::CreateInstance with a TypeSystemSwiftTypeRef, the other version works as expected.

  • Explanation:
    This fixes an issue in one version SwiftASTContext::CreateInstance where source mappings were not properly applied like they are in the ohter version.

  • Scope:
    Very limited, fixes inconsistent application of target.source-map, no other changes

  • Issues:
    We're seeing ClangImporter failures due to the remappings not being applied, but haven't filed upstream issues.

  • Original PRs: Fix issue where target.source-map didn't apply to SwiftASTContext::CreateInstance #10527

  • Risk: Low, only applies to lldb sessions with target.source-map and is a correctness fix. The previous behavior is incorrect.

  • Testing: All tests passed. Tried to update TestSwiftRewriteClangPaths but was able to trigger the modified version of SwiftASTContext::CreateInstance, I think a new test suite can be added / this test could be modified in a follow up if needed.

  • Reviewers:
    Not yet approved, TBD

…eateInstance

This specifically is for SwiftASTContext::CreateInstance with a
TypeSystemSwiftTypeRef, the other version works as expected.
@DavidGoldman
Copy link
Author

@swift-ci please test

@adrian-prantl adrian-prantl merged commit dc1beb9 into swiftlang:swift/release/6.2 May 2, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants