-
Notifications
You must be signed in to change notification settings - Fork 37
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
: loopPre
is defined twice
#438
Comments
My intuition here would be to just remove the one in |
Hi, I'd like to work on this issue. The second approach seems less likely to break the API, so I would perhaps go with that? |
Great! Yeah, let's go with the second approach. Can you please structure it this way?
Always reference the issue with Do you think you can have it ready today? I need to have the next release ready tonight (EOB Pacific time). |
I applied the changes in #441. The duplicate definition of |
Thanks! I responded in the PR. |
…keera#438. The function loopPre is defined twice: once in FRP.BearRiver, and once in FRP.BearRiver.Loop. Only one definition should be needed. This prevents FRP.BearRiver from providing an API equivalent to Yampa's. This commit modifies FRP.Yampa to hide the import of loopPre definition from FRP.BearRiver and replaces it by a re-export of FRP.Yampa.Loop.
The function
loopPre
is defined twice: once inFRP.BearRiver
, and once inFRP.BearRiver.Loop
. Only one definition should be needed.This prevents
FRP.BearRiver
from providing an API equivalent to Yampa's.The text was updated successfully, but these errors were encountered: