core.async pipeline bug?

[Paul Rutledge]

Hi all,

I've been using the 'pipeline' function in core.async and the docstring says that the 'from' channel won't be consumed anymore after the 'to' channel is closed (since you probably don't care anymore). In reality, I'm finding that my 'from' channel is still being taken from and the pipeline transducer continues to execute long after I've closed the 'to' channel. Am I misunderstanding the stated behavior or is this a bug? I'm using the latest version (0.4.474). If someone can confirm this is an issue I'm happy to create a jira ticket and attempt a patch.

Minimal example here: https://gist.github.com/RutledgePaulV/6ddb7b29578de4442cd8d946885c38a8

Thanks,

Paul

[Alex Miller]

Is the scenario this one?

https://dev.clojure.org/jira/browse/ASYNC-217

[Paul Rutledge]

Sure is. Thanks Alex!

On Tue, Sep 4, 2018, 6:21 AM Alex Miller <al...@puredanger.com> wrote:

Is the scenario this one?

https://dev.clojure.org/jira/browse/ASYNC-217

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "Clojure" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/clojure/neUNL6Lcs2o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to clojure+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.