Skip to content
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

fresh variables on each iteration in nested loop and generator syntax #26483

Merged
merged 1 commit into from
Mar 19, 2018

Conversation

JeffBezanson
Copy link
Sponsor Member

On the plus side, I get to close a 3-digit issue. On the minus side, that is some grödy lowering 😁

I think these cases are rare enough that we can live without a deprecation. It's a small miracle that the deprecation for the other loop scope change still works with this. But there is a strange interaction: for all but the innermost loop variable, you can still get scope deprecation warnings, but you can't assign to the outer variable from the loop body (unless it's declared outer).

fixes #330

@JeffBezanson JeffBezanson added kind:breaking This change will break code compiler:lowering Syntax lowering (compiler front end, 2nd stage) labels Mar 16, 2018
@JeffBezanson JeffBezanson merged commit 0fffb36 into master Mar 19, 2018
@JeffBezanson JeffBezanson deleted the jb/loopnests branch March 19, 2018 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler:lowering Syntax lowering (compiler front end, 2nd stage) kind:breaking This change will break code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

potentially confusing behavior in cartesian loops
1 participant