Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Full pipes compatibility #7

Open
tomjaguarpaw opened this issue Jan 30, 2016 · 0 comments
Open

Full pipes compatibility #7

tomjaguarpaw opened this issue Jan 30, 2016 · 0 comments

Comments

@tomjaguarpaw
Copy link

This is a very cool library! I like how general it is.

The definition of Proxy from pipes is

data Proxy a' a b' b m r
    = Request a' (a  -> Proxy a' a b' b m r )
    | Respond b  (b' -> Proxy a' a b' b m r )
    | M          (m    (Proxy a' a b' b m r))
    | Pure    r

It seems like you can replicate this in streaming by Stream (Proxy a' a b' b) m r where

data Proxy a' a b' b z
    = Request a' (a  -> z)
    | Respond b  (b' -> z)

(a different Proxy, of course). Any interest in adding something like this? I'm not going to use it now but I thought it was worth recording .

mitchellwrosen pushed a commit to mitchellwrosen/streaming that referenced this issue Dec 9, 2017
`mapsExposed` was just a copy of `maps`, and `mapsMExposed` was just
a copy of `mapsM`. As far as I can tell, neither of them does anything
that exposes the abstraction, so there's no point in having these
scarily-named versions.

Fixes michaelt#7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant