Those are Elm 0.16 effects are something totally different. There is no > reason why tick tasks couldn't be batched in their execution.
I disagree. I said I’m not authoritative, and meant that I can’t speak for *all* the possible reasons that Task and Cmd cannot be unified into one concept. But what I can say is: - Elm 0.16 effects are not something totally different. In fact, the Effects type from that package is the direct predecessor of the Cmd type, and the implementation of the “tick batching trick” was the first nontrivial effect manager (though that concept didn’t have a name back then). If you can substantiate the claim that 0.16’s Effects and 0.17’s Cmd type constructors are totally different, I would be interested to hear the argument. - I was the person who implemented the “tick batching trick” back then. I can tell from that experience that to make it work, an abstraction was needed (but preexisting, not “invented” by me) that absolutely mustn’t support an andThen operation like Task does. So on that specific count, I can with a bit of authority contradict your assertion that there is no reason why tick tasks couldn’t be batched (with the same quality as Effects/Cmds can). -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
