Basically, the newly added `withSpawn` combinator is safe to use
(https://github.com/Gabriel439/Haskell-Pipes-Concurrency-Library/pull/33#issuecomment-71329094).
If you only use that you won't have any issues. It's not as flexible as
the garbage-collection approach, but you may not need the extra
flexibility. I haven't uploaded that combinator yet, but I will soon
(and it's pretty easy to inline in your own code: it's just `bracket`).
The only reason I haven't completely deprecated the
garbage-collection-based approach is that Carter indicated to me that he
might know what caused the regression and I would like to fix it if
possible since it's a really useful feature.
On 1/26/15, 10:50 AM, Ben Moseley wrote:
I'm wondering what the current state-of-play is with pipes-concurrency.
It looks interesting, but I'm made somewhat nervous about adopting it
in anger by:
https://github.com/Gabriel439/Haskell-Pipes-Concurrency-Library/issues/27
https://github.com/Gabriel439/Haskell-Pipes-Concurrency-Library/issues/28
https://github.com/Gabriel439/Haskell-Pipes-Concurrency-Library/issues/29
https://www.haskell.org/pipermail/glasgow-haskell-users/2014-July/025107.html
Also, presumably if pipes-concurrency is unsound, then so are mvc,
pipes-postgresql-simple, process-streaming etc as they all depend on it...
Can anyone comment?
--Ben
--
You received this message because you are subscribed to the Google
Groups "Haskell Pipes" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to haskell-pipes+unsubscr...@googlegroups.com
<mailto:haskell-pipes+unsubscr...@googlegroups.com>.
To post to this group, send email to haskell-pipes@googlegroups.com
<mailto:haskell-pipes@googlegroups.com>.
--
You received this message because you are subscribed to the Google Groups "Haskell
Pipes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to haskell-pipes+unsubscr...@googlegroups.com.
To post to this group, send email to haskell-pipes@googlegroups.com.
