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

Fix: poisoned next function in "IteratorClose is called when reference evaluation produces a "return" completion". Fixes gh-670 #2820

Merged
merged 2 commits into from Sep 25, 2020

Conversation

rwaldron
Copy link
Contributor

No description provided.

@rwaldron rwaldron force-pushed the no-next-function-for-iterator-670 branch from b5d27da to ee42c17 Compare September 25, 2020 16:04
@rwaldron rwaldron force-pushed the no-next-function-for-iterator-670 branch from ee42c17 to 6f15554 Compare September 25, 2020 16:59
@rwaldron rwaldron merged commit 73db72b into main Sep 25, 2020
@rwaldron rwaldron deleted the no-next-function-for-iterator-670 branch September 25, 2020 17:15
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.

None yet

1 participant