Skip to content

Also initialize the per-module SwiftASTContext using ProcessModule() #8774

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
merged 3 commits into from
May 21, 2024

Conversation

adrian-prantl
Copy link

this resolves some inconsistencies in search path resolution between
the expression context and SwiftASTContextForModule().

rdar://127776675

@adrian-prantl
Copy link
Author

@swift-ci test

@adrian-prantl
Copy link
Author

@swift-ci test

@adrian-prantl
Copy link
Author

@swift-ci test

@adrian-prantl
Copy link
Author

@swift-ci test linux

@adrian-prantl
Copy link
Author

test with swiftlang/swift#73757

@adrian-prantl
Copy link
Author

test with swiftlang/swift#73757
@swift-ci test linux

@adrian-prantl
Copy link
Author

@swift-ci test

since it will use the per-module scratch context, and not the
per-symbolcontext one.

This codepath is only exercised when the type ref typesystem is turned
off.
this resolves some inconsistencies in search path resolution between
the expression context and SwiftASTContextForModule().

rdar://127776675
@adrian-prantl
Copy link
Author

@swift-ci test

@adrian-prantl adrian-prantl merged commit 4218d86 into swiftlang:swift/release/6.0 May 21, 2024
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