-
Notifications
You must be signed in to change notification settings - Fork 36
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
bearriver
: the function reactimate
is API-incompatible
#454
Comments
If someone wants to do this, please go ahead and send a PR. Please create 2 commits:
Please check out the recent history of this repository to see how we normally document commits, and how we link commits to issues in the subject line of the commit messages. Make sure you use There was a similar issue with |
I'm trying to implement this with
This hole is
But now I need |
I think the clue is: foldIdentity :: Monad m => SF a b -> BR.SF m a b
foldIdentity = morphS $ mapReaderT $ return . runIdentity |
Hi @solomon-b . Did you get a chance to try this idea? |
Not yet, but I plan to work on it this weekend. |
Hi @solomon-b . Let me know if you want me to take a look at something, even if it's not complete. Thanks! |
@ivanperez-keera I'm sorry for the delay. Work got really busy but I have time this weekend (for real this time). I'll get something together by end of day tomorrow. |
The function
reactimate
doesn't have the same signature as in Yampa: inbearriver
it forces the monad of the SF to be the same as the monad of the sensing/actimation actions and reactimate itself, but a Yampa SF is mapped to a Bearriver SF on the Identity monad.This makes modules that use Yampa's
reactimate
not API-compatible with bearriver.Bearriver's
FRP.Yampa
module should hideFRP.BearRiver.reactimate
and define one inFRP.Yampa
that has the same signature as Yampa's (likely relying onFRP.BearRiver.reactimate
via a qualified import).The text was updated successfully, but these errors were encountered: