Part of what makes runtime exceptions not inevitable is that many such errors come from I/O actions, which Elm handles with care. If you have a specific example of an inevitable runtime error, we'd like to hear it.
Theoretically of course, Elm doesn't solve the halting problem and you can always blow the stack or exhaust memory. So it's not terrible that any function can call Debug.crash, which is an uncatchable exception. It's useful for when you think something can never, ever, happen. -- 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.
