-
Notifications
You must be signed in to change notification settings - Fork 70
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
small refactor: make BuildW a proper data type #275
Conversation
where | ||
pulse = _nodeP pulse0 | ||
parent = _nodeP parent0 | ||
|
||
liftIOLater :: IO () -> Build () | ||
liftIOLater x = RW.tell $ BuildW (mempty, mempty, Action x, mempty) | ||
liftIOLater x = RW.tell mempty { bwLateIO = Action x } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
liftIOLater x = RW.tell mempty { bwLateIO = Action x } | |
liftIOLater x = RW.tell emptyBuildW{ bwLateIO = Action x } |
Two requests on the matter of record syntax:
mempty
is too generic a name. Could you defineemptyBuildW = mempty
, so that it better resembles theBuildW
constructor?- Record syntax messes a little with the "spaces separate distinct arguments" rule. Could you remove the spaces between the value and
{
? In this way, it becomes visually clear that{
modifies the value.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You got it!
|
@HeinrichApfelmus I think this is good to go |
Thanks! 😊 |
This PR just gives field names to each of the four components of a
BuildW
.This would be a breaking change requiring a major version bump, except
BuildW
is conspicuously missing from the export list of Reactive.Banana.Prim.Mid - unless we say that module doesn't follow the PVP - but was not exportingBuildW
intentional?