Changeset 814f87d for doc/theses/andrew_beach_MMath/intro.tex

Timestamp:

Sep 23, 2021, 3:36:04 PM (3 years ago)

Author:

Andrew Beach <ajbeach@…>

Branches:

ADT, ast-experimental, enum, forall-pointer-decay, master, pthread-emulation, qualifiedEnum

Children:

9411cf0

Parents:

75c7252

Message:

Andrew MMath: Updated thesis with Yizhou Zhang's feedback.

File:

• doc/theses/andrew_beach_MMath/intro.tex (modified) (3 diffs)

doc/theses/andrew_beach_MMath/intro.tex

@@ -220 +220 @@
 unwinding the stack like in termination exception
 handling.\cite{RustPanicMacro}\cite{RustPanicModule}
-Go's panic through is very similar to a termination, except it only supports
+Go's panic though is very similar to a termination, except it only supports
 a catch-all by calling \code{Go}{recover()}, simplifying the interface at
 the cost of flexibility.\cite{Go:2021}
@@ -265 +265 @@
 This pattern is very popular in any functional or semi-functional language
 with primitive support for tagged unions (or algebraic data types).
-% We need listing Rust/rust to format code snippets from it.
-% Rust's \code{rust}{Result<T, E>}
+Return unions can also be expressed as monads (evaluation in a context)
+and often are in languages with special syntax for monadic evaluation,
+such as Haskell's \code{haskell}{do} blocks.
+
 The main advantage is that an arbitrary object can be used to represent an
 error, so it can include a lot more information than a simple error code.
@@ -272 +274 @@
 execution, and if there aren't primitive tagged unions proper, usage can be
 hard to enforce.
+% We need listing Rust/rust to format code snippets from it.
+% Rust's \code{rust}{Result<T, E>}
+
+Return unions as monads will result in the same code, but can hide most
+of the work to propagate errors in simple cases. The code to actually handle
+the errors, or to interact with other monads (a common case in these
+languages) still has to be written by hand.
 
 \item\emph{Handler Functions}: