Skip to content

Preliminary steps towards support for closures that capture pack element environments #73348

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

slavapestov
Copy link
Contributor

@slavapestov slavapestov commented Apr 30, 2024

This is just some NFC refactoring split off from a larger PR. The only notable thing is that CaptureInfo records a stack of GenericEnvironments now, but they're not used anywhere yet.

The discriminator assignment has since been split off into a separate
thing, so all this does now is re-parent children of autoclosures.
We walk up the DeclContext hierarchy looking for closures, but they might
not have had their types set yet because they're currently being type
checked.
@slavapestov slavapestov force-pushed the pack-expansion-closures-part-1 branch from f091f16 to a480f8b Compare April 30, 2024 20:10
…mary environment

I suspect there are latent bugs here with generic-class-constrained existentials,
same-element requirements involving packs, etc. We can't assume that the
local archetypes don't have "hidden" dependencies on the outer parameters
that are not encoded in the thunk's interface type.
@slavapestov slavapestov force-pushed the pack-expansion-closures-part-1 branch from a480f8b to 865b155 Compare May 1, 2024 02:47
@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test

@slavapestov
Copy link
Contributor Author

@swift-ci Please test source compatibility

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.

1 participant