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.

Sign up for GitHub

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

Jump to bottom

go-for can cause too many pending puts. #1

Open
whilo opened this issue Oct 17, 2016 · 0 comments
Open

go-for can cause too many pending puts. #1

whilo opened this issue Oct 17, 2016 · 0 comments

Comments

@whilo
Copy link
Member

whilo commented Oct 17, 2016

When using the go-for macro with nested loops, core.async can trigger a "too many pending puts" assertion. This shouldn't happen, values should be produced lazily.
TimoKramer pushed a commit to TimoKramer/superv.async that referenced this issue May 26, 2021
@groundedsage
Merge pull request replikativ#1 from TimoKramer/build-tool-migration
bc1bf6e 
Add CI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@whilo