tag:blogger.com,1999:blog-1777990983847811806.post988803969804139223..comments2024-03-16T16:29:29.582-07:00Comments on Haskell for all: pipes-concurrency-1.0.0: Reactive programmingGabriella Gonzalezhttp://www.blogger.com/profile/01917800488530923694noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-1777990983847811806.post-72294179020441731042015-04-12T20:18:35.255-07:002015-04-12T20:18:35.255-07:00Hitting it out of the park, once again! Your libra...Hitting it out of the park, once again! Your libraries alone demonstrate Haskell's importance and value for front-line development.Anonymoushttps://www.blogger.com/profile/18335957121025186789noreply@blogger.comtag:blogger.com,1999:blog-1777990983847811806.post-74463664674460769472013-06-08T08:21:02.126-07:002013-06-08T08:21:02.126-07:00There are two main reasons:
* To avoid an `async`...There are two main reasons:<br /><br />* To avoid an `async` dependency<br /><br />* There may be more run functions than just `runProxy` (i.e. `runEitherK`, `evalStateK`), especially if using `pipes-safe`.Gabriella Gonzalezhttps://www.blogger.com/profile/01917800488530923694noreply@blogger.comtag:blogger.com,1999:blog-1777990983847811806.post-49317408077646866442013-06-08T07:07:59.085-07:002013-06-08T07:07:59.085-07:00I see this pattern is used regularly, why it isn&#...I see this pattern is used regularly, why it isn't wrapped in a some handy shortcut?<br /><br />> run pipe = async (runProxy pipe >> performGC)<br />IC Rainbowhttps://www.blogger.com/profile/06087844615747674044noreply@blogger.com