Yeah. And considering that the high-level web socket API is held up as the standard of where things are going, it would seem the absence of exposed chainable tasks is likely only to get worse.
Another way to look at this as I think about it is: Why Cmd msg as opposed to Task Never msg as a result type from update functions? Of course, one can return whatever one wants from one's own update functions, but the point is really why Cmds as opposed to Tasks as the standard way to represent work to be done? Mark On Tue, Nov 29, 2016 at 11:14 PM Max Goldstein <[email protected]> wrote: > Hmm. I want to say it's an issue with the library, but fixing it would > involve changing a fair amount of code and using the low level Websocket > API. > > -- > 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. > -- 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.
