The documentation is fixed. Sorry for the delay
On 12/21/15 5:34 AM, Dylan Tisdall wrote:
Hi Gabriel,
Thanks very much for getting to this. Is there a reason why the source
and tutorial seem to be hidden (no clickable links) on Hackage for 2.0.4?
Thanks again,
Dylan
On Dec 19, 2015, at 11:36 PM, Gabriel Gonzalez <gabriel...@gmail.com
<mailto:gabriel...@gmail.com>> wrote:
Alright, this is up on Hackage as `pipes-concurrency-2.0.4`. Sorry
for the delay!
On 12/9/15 11:22 AM, Dylan Tisdall wrote:
That's even better. Thanks!
On Dec 9, 2015, at 2:21 PM, Gabriel Gonzalez <gabriel...@gmail.com
<mailto:gabriel...@gmail.com>> wrote:
Oh, that's just an oversight on my part. I forgot to upload it to
Hackage. I will try to upload it no later than this weekend.
On 12/9/15 10:51 AM, Dylan Tisdall wrote:
Hi Gabriel,
I just wanted to follow up on this, since I couldn't find any more
recent info. It looks like spawnWith isn't in the 2.0.3 version of
pipes-concurrency that's up on hackage. If I'd like to work with
this package in ghc 7.10, do you suggest I copy the spawnWith
function from your repo into my codebase and work from that? Is
there some other issue that came up that would lead you to suggest
not using spawnWith now?
Thanks,
Dylan
On Monday, January 26, 2015 at 2:22:24 PM UTC-5, Gabriel Gonzalez
wrote:
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/27>
https://github.com/Gabriel439/Haskell-Pipes-Concurrency-Library/issues/28
<https://github.com/Gabriel439/Haskell-Pipes-Concurrency-Library/issues/28>
https://github.com/Gabriel439/Haskell-Pipes-Concurrency-Library/issues/29
<https://github.com/Gabriel439/Haskell-Pipes-Concurrency-Library/issues/29>
https://www.haskell.org/pipermail/glasgow-haskell-users/2014-July/025107.html
<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-pipe...@googlegroups.com
<javascript:>.
To post to this group, send email to haskel...@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
<mailto:haskell-pipes+unsubscr...@googlegroups.com>.
To post to this group, send email to 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.
