Skip to content

Retire DynamicValueTypeInfoNeedsUpdate() (NFC) #8386

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 1 commit into from
Mar 13, 2024

Conversation

adrian-prantl
Copy link

This function was introduced to detect a stale Swift scratch context. Today it doesn't make much sense, since all ValueObjects prefer to store their types as TypeSystemSwiftTypeRef types, and dynamic type resolution is done using type metadata, and not in SwiftASTContext space. This avoids a very costly initialization of the Swift compiler triggered by ValueObjectDynamicValue.

rdar://124487859

This function was introduced to detect a stale Swift scratch
context. Today it doesn't make much sense, since all ValueObjects
prefer to store their types as TypeSystemSwiftTypeRef types, and
dynamic type resolution is done using type metadata, and not in
SwiftASTContext space. This avoids a very costly initialization of the
Swift compiler triggered by ValueObjectDynamicValue.

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

@swift-ci test

Copy link

@kastiglione kastiglione left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice

@adrian-prantl adrian-prantl merged commit a9056fe into swiftlang:stable/20230725 Mar 13, 2024
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