Can your stream processing library do this?This talk is my attempt to better understand the design space for stream processing and safe functional IO - there are a lot of different APIs - lazy io, iteratees (pure and monadic), iteratees+monadic regions, conduits, pipes, and even FRP - but what are the differences between them? Do they fully solve the problem of safe, streaming IO? I will present a series of concrete stream processing scenarios / use-cases, discuss how various approaches fare at expressing them in a compositional, resource-safe way, and talk about some general themes that emerge.
On Tue, May 15, 2012 at 4:12 PM, Edward Kmett <ekm...@gmail.com> wrote:Thanks. This works.
> The Boston Haskell mailing list is hosted by google groups, so the post can
> be found here
>
> https://groups.google.com/forum/?fromgroups#!topic/bostonhaskell/3yDmOVTIc0o
>
Obviously, a message can't announce its own URL;
and yet, it might including a nonce in the message and pointing to
a search link for same in designated group
(even better if there's a way to select the oldest such message).
> and I followed up with a post to Google+, which I think should reachable"This post could not be found.
> from the following URL:
>
> https://plus.google.com/113063331545548237308/posts/U7gwZbiVKi9
>
Your URL may be incorrect, the post may have been deleted,
or this account may not have access to the post."
Maybe it's not public.
So you guys have me curious. I've been on this list for awhile, since I spent ~6 months of my PhD formalizing a set-theoretic aspect of my research using Haskell, but that was ~7 years ago.
Are you interested in people like me (really *non*-Haskellites) talking about how they've used Haskell (and showing off working code)?
If so, I'd be happy to do it, but only if there are promises of "constructive criticism" and no tomato throwing.
I ask partially because I never published this aspect of my work and am thinking about doing so now. Dusting it off and getting some feedback would be helpful to me. I think the work is reasonably interesting (models for SLAs and market agreements/contract formation).\