Skip to content

[5.8][CSGen] Handle recursive use of variable declarations #63551

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

Closed
wants to merge 1 commit into from

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Feb 9, 2023

Cherry-pick of #63505


It's possible for out-of-scope type variable to be the type
of declaration if such declaration is recursively referenced
in the body of a closure located in its initializer expression.
In such cases type of the variable declaration cannot be
connected to the closure because its not known in advance
(determined by the initializer itself).

Resolves: #63455 (cherry picked from commit 83dd93a)

It's possible for out-of-scope type variable to be the type of
declaration if such declaration is recursively referenced in
the body of a closure located in its initializer expression.
In such cases type of the variable declaration cannot be connected
to the closure because its not known in advance (determined by the
initializer itself).

Resolves: swiftlang#63455
(cherry picked from commit 83dd93a)
@xedin xedin requested a review from hborla February 9, 2023 19:22
@xedin xedin requested a review from a team as a code owner February 9, 2023 19:22
@xedin xedin added swift 5.8 🍒 release cherry pick Flag: Release branch cherry picks labels Feb 9, 2023
@xedin
Copy link
Contributor Author

xedin commented Feb 9, 2023

@swift-ci please test

@xedin
Copy link
Contributor Author

xedin commented Feb 11, 2023

I am closing this one because it causes source compatibility regressions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🍒 release cherry pick Flag: Release branch cherry picks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants