Mitchell Dalvi Rosen

It's just the first solution that came to mind, and it'd actually make the code a bit cleaner. The real type signature for `makeTickEvent` is ```haskell makeTickEvent :: Int --...

Hmm... no strong feelings either way :sweat_smile:. In defense of the status quo, I've only ever called `compile` at type `MomentIO ()`, so I'd never have preferred this variant which...

Good point, I like that pattern. Ok, I switch to (2), then (3), then (1).

I agree with @ocharles, but I get where @HeinrichApfelmus is coming from. I think the pattern of "don't return this value here, which we do not attempt to prevent with...

The initial value doesn't fire for `stepper`/`accumB` either. This seems preferable to me.

Nice, can you share how you made the pretty graph?

@greyson This is possible with the current API assuming you have some `Behavior v` to use before any `Event k` fires: ```haskell bMap :: Behavior (Map K (Behavior V)) eKey...

I'm sorry I don't totally understand your example, but it's possible you can benefit from simply keeping a `Behavior` and the `Event` that steps it forward together in the same...

@lobachevzky The `custom-setup` stanza is top-level (it allows you to specify dependencies of `runhaskell Setup.hs` itself)

Try putting this in your `stack.yaml`: ``` explicit-setup-deps: - reactive-banana-wx: true ```