Skip to content

Restore the per-module scratch context fallback mechanism. #5308

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

adrian-prantl
Copy link

This feature has been accidentally disabled when introducing
TypeSystemSwiftTypeRefForExpressions and thanks to how good
TypeSystemSwiftTypeRef has become, all of the tests for the feature
were still passing.

When the copy constructor is called m_readers needs to be incremented
because the destructor will be calkled on both the original object and
the copy.
so it can (in a follow-up commit) be initialized with the current
frame as ExecutionContextScope.

NFC
This feature has been accidentally disabled when introducing
TypeSystemSwiftTypeRefForExpressions and thanks to how good
TypeSystemSwiftTypeRef has become, all of the tests for the feature
were still passing.
@adrian-prantl
Copy link
Author

@swift-ci test

@adrian-prantl
Copy link
Author

ping

@adrian-prantl adrian-prantl merged commit c205842 into swiftlang:stable/20220421 Sep 21, 2022
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