Ryan Trinkle

In this case, I think what we need to do is write up an example of how to use selectElement that we can link people to.

The purpose of the postBuild event is just to fire as soon as possible after the builder action has finished running, so this is the intended behavior. It's not meant...

What do you think about something like a Dynamic that represents the current state? Then, the 'updated' state could be used to detect state changes.

In theory, this shouldn't be too hard, and I'm pretty sure some people have done it. You could try using [`justStaticExecutables`](https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/haskell-modules/lib.nix#L244) on the frontend Nix derivation, which might get you...

I don't think there's a major problem with us changing the way we invoke hlint, if that is helpful. On Tue, Jun 11, 2019 at 8:54 PM endgame wrote: >...

@2426021684 This is very similar to [`runWithReplace`](https://github.com/reflex-frp/reflex/blob/c810e6a20310e1e681bd11511e59eaae393c68df/src/Reflex/Class.hs#L1164). Would that be helpful here? One of the rules we try to abide by in all our widget code is not to be...

@lspitzner What are the semantics you're looking for? E.g.: if we produce `out` using this, when should `updated out` fire, and what should be the value of `current out` at...

I thought about these some more, and I think these functions can't be written. In the case of `f :: (a -> b -> c) -> Behavior a -> Dynamic...

The function with that exact type signature is [`unsafeDynamic`](https://github.com/reflex-frp/reflex/blob/36db894180d015fdd032d7d3a338e0b5ac9df4b4/src/Reflex/Class.hs#L426). It's unsafe because it has no way to know whether your `Event` and `Behavior` obey the Dynamic law. [`buildDynamic`](https://github.com/reflex-frp/reflex/blob/60d2878142943487987feeeea108dbed5405f469/src/Reflex/Class.hs#L465), on the...

FWIW, I've found that `unsafeDynamic` is surprisingly difficult to use properly. I wouldn't recommend it if you have any other options.