Skip to content

[5.0] KeyPath: Allow existing context descriptors to be used as generic environment. #21214

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

Conversation

jckarter
Copy link
Contributor

If a key path literal appears in a generic context with an existing context descriptor, this will allow us to
save some code size by not having to emit a separate GenericEnvironment descriptor. rdar://problem/46633593

This is an additive ABI change. It is not necessary for convergence.

@jckarter jckarter requested a review from a team as a code owner December 11, 2018 18:45
@jckarter
Copy link
Contributor Author

@swift-ci Please test

@swift-ci
Copy link
Contributor

Build failed
Swift Test Linux Platform
Git Sha - 0df51fa58adcbd05c45b6c3786217270c85ec217

@swift-ci
Copy link
Contributor

Build failed
Swift Test OS X Platform
Git Sha - 0df51fa58adcbd05c45b6c3786217270c85ec217

@jckarter
Copy link
Contributor Author

Oops, this will merge conflict with #21213, so I'll wait to update till that's merged.

…ironment.

If a key path literal appears in a generic context with an existing context descriptor, this will allow us to
save some code size by not having to emit a separate GenericEnvironment descriptor.
@jckarter jckarter force-pushed the key-path-generic-environment-or-context-5.0 branch from 0df51fa to df523d4 Compare December 12, 2018 02:47
@jckarter
Copy link
Contributor Author

@swift-ci Please test

@swift-ci
Copy link
Contributor

Build failed
Swift Test Linux Platform
Git Sha - 0df51fa58adcbd05c45b6c3786217270c85ec217

@swift-ci
Copy link
Contributor

Build failed
Swift Test OS X Platform
Git Sha - 0df51fa58adcbd05c45b6c3786217270c85ec217

@AnnaZaks AnnaZaks merged commit c786ca4 into swiftlang:swift-5.0-branch Dec 12, 2018
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.

3 participants