Peter Duchovni

This might not be entirely practical with the specific implementations of Event and Behavior, but I have a mockup of a `` operator and a complementary `` operator that work...

@HeinrichApfelmus I agree with you that `` is a rather unfortunate name, though I chose it just for the purposes of the mock-up. I also figured that for Behavior, an...

Just my two cents, but this may be helpful. Not sure what is actually possible or feasible, but this is how I would do it if all the right features...

I would also be satisfied by something of the type `Behavior (Behavior a) -> Moment (Behavior a)`, as many of the Behavior/Event manipulation I am dealing with happens inside of...

Just follow-up on the problem I was having; this is probably the right way according to the philosophy of your code, but I handled the display matter with an event...

@vdukhovni recruited me to work on implementing new read/show instances for the various types still missing them, and i went ahead and developed a more robust paradigm for easily implementing...

This patch constitutes an API change that would potentially break network-dependent packages depending on how reliant they are on the reflection `ProtocolNumber ~ CInt`. It may require a code-survey of...

I also noticed that an incomplete pattern warning for Network/Socket/Types.hsc can be fixed by replacing ```haskell isSupportedFamily :: Family -> Bool isSupportedFamily f = case f of UnsupportedFamily -> False...

I am currently trying to assess how big an impact this API change would have on existing libraries, and have also requested an external reviewer independently. For now, I don't...