Tyson Williams

Can you share a specific example that is implemented twice: once for each pattern? I would describe the API in 3.x as having methods to create a binding with a...

Are you still interested in this? If so, can you share some examples?

Furthermore, the advantage of the last case increases when considering the more complicated variant of `update` that also returns the `Cmd`s to execute.

That last approach would also make it possible to send no messages, which is also something I want to do sometimes. My current workaround is to create a message called...

My plan is for an easy change. Mostly just a couple compostable functions. I will reply more here and elsewhere within the next couple days.

> Do you want to go for a breaking change and only have the list API? No. I have already introduced one breaking change in v4, which is the removal...

I also meant to explicitly say... I still like idea of a method-based API both because it is more terse and because it can help improve discoverability.

Initially, no changes to the method-based API

(To repeat myself and/or add to what I said and/or summarize what I said) I want to expose everything that is possible via the function-based binding API. Then we can...

(Meta: @Evangelink, I believe that I have now replied or processed all of your recent communication. If you are still expecting a reply from me somewhere, just let me know.)