diff options
Diffstat (limited to 'docs/ERRORS.md')
| -rw-r--r-- | docs/ERRORS.md | 99 |
1 files changed, 56 insertions, 43 deletions
diff --git a/docs/ERRORS.md b/docs/ERRORS.md index cce29c1..665535f 100644 --- a/docs/ERRORS.md +++ b/docs/ERRORS.md @@ -1,83 +1,96 @@ # Error Handling -Puck's error handling is shamelessly stolen from Swift. It uses a combination of `Option`/`Result` types and `try`/`catch` statements, and leans somewhat on Puck's metaprogramming capabilities. +Puck's error handling is heavily inspired syntactically by Swift and semantically by the underlying effects system. It uses a combination of monadic error handling and effectful error propagation, with much in the way of syntactic sugar for conversion between the two, and leans somewhat heavily on Puck's metaprogramming capabilities. In comparison to Rust, it is considerably more dynamic by default. -There are several ways to handle errors in Puck. If the error is encoded in the type, one can: +There are several ways to handle errors in Puck. If the error is encoded in the type (as an `Option` or `Result` type), one can: 1. `match` on the error 2. compactly match on the error with `if ... of` 3. propagate the error with `?` 4. throw the error with `!` -If an error is thrown, one **must** explicitly handle (or disregard) it with a `try/catch` block or risk runtime failure. This method of error handling may feel more familiar to Java programmers. +If the error is thrown (encoded as an effect), one can: +1. ignore the error, propagating it up the call stack +2. recover from the error in a `try` block +3. convert the error to a `Result[T]` (monadic form) -## Errors as Monads +If an error is thrown, one *must* explicitly handle it at some level of the stack, or risk runtime failure. This method of error handling may feel more familiar to Java programmers. The compiler will warn on - but not enforce catching - such unhandled errors. -Puck provides [`Option[T]`](std/default/options.pk) and a [`Result[T, E]`](std/default/results.pk) types, imported by default. These are `union` types and so must be pattern matched upon to be useful: but the standard library provides [a bevy of helper functions](std/default/results.pk). +## Errors as monads + +Puck provides [`Option[T]`](std/default/options.pk) and a [`Result[T, E]`](std/default/results.pk) types, imported by default. These are `union` types under the hood and so must be pattern matched upon to be useful: but the standard library provides [a bevy of helper functions](std/default/results.pk). Two in particular are of note. The `?` operator unwraps a Result or propagates its error up a function call (and may only be used in type-appropriate contexts). The `!` operator unwraps an Option or Result directly or throws an exception in the case of None or Error. ```puck -pub macro `?`[T, E](self: Result[T, E]) = - quote: +pub macro ?[T, E](self: Result[T, E]) = + quote match `self` - of Okay(x): x - of Error(e): return Error(e) + of Okay(x) then x + of Error(e) then return Error(e) ``` ```puck -pub func `!`[T](self: Option[T]): T = +pub func : T = match self - of Some(x): x - of None: raise EmptyValue + of Some(x) then x + of None then raise "empty value" -pub func `!`[T, E](self: Result[T, E]): T = - of Okay(x): x - of Error(e): raise e +pub func : T = + match self + of Okay(x) then x + of Error(e) then raise e ``` -The utility of the provided helpers in [`std.options`](std/default/options.pk) and [`std.results`](std/default/results.pk) should not be understated. While encoding errors into the type system may appear restrictive at first glance, some syntactic sugar goes a long way in writing compact and idiomatic code. Java programmers in particular are urged to give type-first errors a try, before falling back on unwraps and `try`/`catch`. - -A notable helpful type is the aliasing of `Result[T]` to `Result[T, ref Err]`, for when the particular error does not matter. This breaks `try`/`catch` exhaustion (as `ref Err` denotes a reference to *any* Error), but is particularly useful when used in conjunction with the propagation operator. +The utility of the provided helpers in [`std.options`](std/default/options.pk) and [`std.results`](std/default/results.pk) should not be understated. While encoding errors into the type system may appear restrictive at first glance, some syntactic sugar goes a long way in writing compact and idiomatic code. Java programmers in particular are urged to give type-first errors a try, before falling back on unwraps and `try`/`with`. -## Errors as Catchable Exceptions +A notable helpful type is the aliasing of `Result[T]` to `Result[T, ref Err]`, for when the particular error does not matter. This breaks `match` exhaustion (as `ref Err` denotes a reference to *any* Error), but is particularly useful when used in conjunction with the propagation operator. -Errors raised by `raise`/`throw` (or subsequently the `!` operator) must be explicitly caught and handled via a `try`/`catch`/`finally` statement. -If an exception is not handled within a function body, the function must be explicitly marked as a throwing function via the `yeet` prefix (name to be determined). The compiler will statically determine which exceptions in particular are thrown from any given function, and enforce them to be explicitly handled or explicitly ignored. +## Errors as checked exceptions -Despite functioning here as exceptions: errors remain types. An error thrown from an unwrapped `Result[T, E]` is of type `E`. `catch` statements, then, may pattern match upon possible errors, behaving similarly to `of` branches. +Some functions do not return a value but can still fail: for example, setters. This can make it difficult to do monadic error handling elegantly. One could return a `type Success[E] = Result[void, E]`, but such an approach is somewhat inelegant. Instead: we treat an `assert` within a function as having an *effect*: a possible failure, that can be handled and recovered from at any point in the call stack. If a possible exception is not handled within a function body, the function is implicitly marked by the compiler as throwing that exception. ```puck -try - ... -catch "Error" then - ... -finally - ... -``` +pub type list[T] = struct + data: ptr T + capacity: uint + length: uint -This creates a distinction between two types of error handling, working in sync: functional error handling with [Option](https://en.wikipedia.org/wiki/Option_type) and [Result](https://en.wikipedia.org/wiki/Result_type) types, and object-oriented error handling with [catchable exceptions](https://en.wikipedia.org/wiki/Exception_handling). These styles may be swapped between with minimal syntactic overhead. Libraries, however, should universally use `Option`/`Result`, as this provides the best support for both styles. - -<!-- [nullable types](https://en.wikipedia.org/wiki/Nullable_type)?? --> +@[safe] +pub func set[T](self: list[T], i: uint, val: T) = + if i > self.length then + raise IndexOutOfBounds + self.data.set(offset = i, val) -## Errors and Void Functions +var foo = ["Hello", "world"] +foo.set(0, "Goodbye") # set can panic +# this propagates an IndexOutOfBounds effect up the call stack. +``` -Some functions do not return a value but can still fail: for example, setters. -This can make it difficult to do monadic error handling elegantly: one could return a `Result[void, E]`, but... +Despite functioning here as exceptions: errors remain types. An error thrown from an unwrapped `Result[T, E]` is of type `E`. `with` statements, then, may pattern match upon possible errors, behaving semantically and syntactically similarly to `of` branches: though notably not requiring exhaustion. ```puck -pub func set[T](self: list[T], i: uint, val: T) = - if i > self.length then - raise IndexOutOfBounds - self.data.raw_set(offset = i, val) +try + foo.set(0, "Goodbye") +with IndexOutOfBounds(index) then + dbg "Index out of bounds at {}".fmt(index) + panic +finally + ... ``` -## Unrecoverable Exceptions +This creates a distinction between two types of error handling, working in sync: functional error handling with [Option](https://en.wikipedia.org/wiki/Option_type) and [Result](https://en.wikipedia.org/wiki/Result_type) types, and [object-oriented error handling](https://en.wikipedia.org/wiki/Exception_handling) with [algebraic effects](...). These styles may be swapped between with minimal syntactic overhead. It is up to libraries to determine which classes of errors are exceptional and best given the effect treatment and which should be explicitly handled monadically. Libraries should tend towards using `Option`/`Result` as this provides the best support for both styles (thanks to the `!` operator). + +## Unrecoverable exceptions There exist errors from which a program can not reasonably recover. These are the following: -- `Assertation Failure`: a call to an `assert` function has returned false at runtime. +- `Assertation Failure`: a call to an unhandled `assert` function has returned false at runtime. - `Out of Memory`: the executable is out of memory. - `Stack Overflow`: the executable has overflowed the stack. - any others? -They are not recoverable, but the user should be aware of them as possible failure conditions. +They are not recoverable, and not handled within the effects system, but the user should be aware of them as possible failure conditions. + +--- -References: [Error Handling in Swift](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/errorhandling) +References +- [Error Handling in Swift](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/errorhandling) +- [Algebraic Effects for the rest of us](https://overreacted.io/algebraic-effects-for-the-rest-of-us/) |