Define common supertype for runtime errors

[munificent]

You can roughly bucket errors into three groups:

1. Programmatic errors: ArgumentError, StateError, etc.
2. System errors: StackOverflow, OutOfMemory, etc.
3. Runtime errors: FormatException, ProcessException, etc.

Occasionally, I find myself wanting to catch all possible runtime errors. (For example, so I can clean up or log on failure.) In those cases, it still feels weird to catch programmatic errors like ArgumentError.

Have you considered having something like:

class Error {} // base class for everything
class Exception extends Error {} // just runtime errors

[lrhn]

You can already catch Exception, which is a supertype of the "Runtime errors".
It's not an Error, though.
Is there something you want to do that you can't just catching Exception?

Distinguishing programmatic errors and system errors is mostly academic, since you are not expected to catch either (unless you are doing fail-safe code, and then you catch everything, not just Exception and Error).

---

Added NeedsInfo label.

[munificent]

Ah, I didn't realize the exception classes were already set up that way. Everything's fine then. :)

---

Added AsDesigned label.