So, Pipes seems fine, but we have a lot of options for streams in Haskell.
Personally I like Streamly a lot.
Streamly has a good tutorial for interop with other libraries, so I have just been converting my Streamly types to Pipes types as the last step before they are fed in as producers. I don't really mind this, but it got me thinking about generalizing the producers in your state reducer. I haven;t looked at the code for the reducer yet, but I don't mind trying to figure it out.
Anyway, If people think this is a good idea I will work on it. If this is somehow not desirable, then I will just leave it alone ;)
So,
Pipesseems fine, but we have a lot of options for streams in Haskell. Personally I likeStreamlya lot.Streamlyhas a good tutorial for interop with other libraries, so I have just been converting my Streamly types toPipestypes as the last step before they are fed in as producers. I don't really mind this, but it got me thinking about generalizing the producers in your state reducer. I haven;t looked at the code for the reducer yet, but I don't mind trying to figure it out.Anyway, If people think this is a good idea I will work on it. If this is somehow not desirable, then I will just leave it alone ;)