I basically look on it as code that exists to make Elm run at all. That's basically what Native exists for. (Native also plays games with the type system but that's another matter.)
And then there's external code that I would like to run that isn't critical to Elm being Elm. That seems a natural place to deploy Tasks. Mark On Tue, Dec 13, 2016 at 8:06 PM, Mark Hamburg <[email protected]> wrote: > Then people would complain that all native calls returned Results rather > than the type they wanted returned. > > Mark > > On Tue, Dec 13, 2016 at 7:42 AM, Joey Eremondi <[email protected]> > wrote: > >> the elm package repo would very quickly get poluted with js code that >>> causes runtime exceptions >> >> >> But, Tasks have error handling built into them. We could do something >> similar with synchronous code, just catch any exceptions thrown, and treat >> the value in Elm as something like a Result. >> >> -- >> 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.
