Transcription

1 Handlers in Action Ohad Kammar University of Cambridge Sam Lindley University of Strathclyde Nicolas Oury Abstract Plotkin and Pretnar s handlers for algebraic effects occupy a sweet spot in the design space of abstractions for effectful computation. By separating effect signatures from their implementation, algebraic effects provide a high degree of modularity, allowing programmers to express effectful programs independently of the concrete interpretation of their effects. A handler is an interpretation of the effects of an algebraic computation. The handler abstraction adapts well to multiple settings: pure or impure, strict or lazy, static types or dynamic types. This is a position paper whose main aim is to popularise the handler abstraction. We give a gentle introduction to its use, a collection of illustrative examples, and a straightforward operational semantics. We describe our Haskell implementation of handlers in detail, outline the ideas behind our OCaml, SML, and Racket implementations, and present experimental results comparing handlers with existing code. Categories and Subject Descriptors D.1.1 [Applicative (Functional) Programming]; D.3.1 [Formal Definitions and Theory]; D.3.2 [Language Classifications]: Applicative (functional) languages; D.3.3 [Language Constructs and Features]; F.3.2 [Semantics of Programming Languages]: Operational semantics Keywords algebraic effects; effect handlers; effect typing; monads; continuations; Haskell; modularity 1. Introduction Monads have proven remarkably successful as a tool for abstraction over effectful computations [4, 30, 46]. However, monads as a programming language primitive violate the fundamental encapsulation principle: program to an interface, not to an implementation. Modular programs are constructed using abstract interfaces as building blocks. This is modular abstraction. To give meaning to an abstract interface, we instantiate it with a concrete implementation. Given a composite interface, each sub-interface can be independently instantiated with different concrete implementations. This is modular instantiation. The monadic approach to functional programming takes a concrete implementation rather than an abstract interface as primitive. For instance, in Haskell we might define a state monad: Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than the author(s) must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from ICFP 13, September 25 27, 2013, Boston, MA, USA. Copyright is held by the owner/author(s). Publication rights licensed to ACM. ACM /13/09... $ newtype State s a = State {runstate :: s (a, s)} instance Monad (State s) where return x = State (λs (x, s)) m >= f = State (λs let (x, s ) = runstate m s in runstate (f x) s ) This definition says nothing about the intended use of State s a as the type of computations that read and write state. Worse, it breaks abstraction as consumers of state are exposed to its concrete implementation as a function of type s (a, s). We can of course define the natural get and put operations on state, but their implementations are fixed. Jones [18] advocates modular abstraction for monads in Haskell using type classes. For instance, we can define the following interface to abstract state computation 1 : class Monad m MonadState s m m s where get :: m s put :: s m () The MonadState interface can be smoothly combined with other interfaces, taking advantage of Haskell s type class mechanism to represent type-level sets of effects. Monad transformers [25] provide a form of modular instantiation for abstract monadic computations. For instance, state can be handled in the presence of other effects by incorporating a state monad transformer within a monad transformer stack. A fundamental problem with monad transformer stacks is that once a particular abstract effect is instantiated, the order of effects in the stack becomes concrete, and it becomes necessary to explicitly lift operations through the stack. Taming the monad transformer stack is an active research area [16, 17, 38, 42]. Instead of the top-down monad transformer approach, we take a bottom-up approach, simply adding the required features as language primitives. We want modular abstraction, so we add abstract effect interfaces, in fact abstract operations, as a language primitive. Abstract operations compose, yielding modular abstraction. We also want modular instantiation, so we add effect handlers as a language primitive for instantiating an abstract operation with a concrete implementation. A handler operates on a specified subset of the abstract operations performed by an abstract computation, leaving the remainder abstract, and yielding modular instantiation. By directly adding the features we require, we obtain modular abstraction and modular instantiation while avoiding many of the pitfalls of monad transformers. Our first inspiration is the algebraic theory of computational effects. Introduced by Plotkin and Power [33 35], it complements Moggi s monadic account of effects by incorporating abstract effect interfaces as primitive. Our second inspiration is the elimination construct for algebraic effects, effect handlers [36]. In Plotkin and Power s setting, one defines algebraic effects with respect to an equational theory. As with other handler implementations [2, 6, 29], 1 From the Monad Transformer Library [12].

2 in this paper we always take the equational theory to be the free theory, in which there are no equations. We argue that algebraic effects and effect handlers provide a compelling alternative to monads as a basis for effectful programming across a variety of functional programming languages (pure or impure, strict or lazy, statically typed or dynamically typed). Our position is supported by a range of handler libraries we have implemented for Haskell, OCaml, SML, and Racket, backed up by a core calculus of effect handlers with a straightforward operational semantics. This paper focuses on the Haskell library. Our key contributions are the following: A collection of novel features for practical programming with handlers in the presence of effect typing, illustrated through a series of examples. A small-step operational semantics for effect handlers. A type and effect system for effect handlers. Effect handler libraries for Haskell, OCaml, SML, and Racket. A performance comparison between our Haskell library and equivalent non-handler code. The rest of the paper is structured as follows. Section 2 presents handlers in action through a series of small examples. Section 3 introduces our core calculus of effect handlers, λ eff, its effect type system, and small-step operational semantics. Section 4 presents in detail the Haskell effect handlers library, and sketches the design of our libraries for OCaml, SML, and Racket. Section 5 reports on the baseline performance of handlers in comparison with existing (less abstract) code. Section 6 discusses related work, and Section 7 concludes. 2. Handlers in Action We present our examples in a monadic style, using an extension to Haskell syntax implemented using the Template Haskell [40] and quasiquote [28] features of GHC. Haskell s features allow for a relatively simple, user-friendly and efficient implementation of effects handlers with effect typing in an existing language. (None of our other libraries support effect typing.) However, all of the examples could in fact be implemented with the same level of expressivity and flexibility in a direct-style, without any monadic boilerplate. Indeed, handlers can be direct-style with or without effect typing, and provide a natural abstraction for adding more controlled effectful computations to the ML family of languages or even to the Lisp family of languages as witnessed by the libraries we have implemented in OCaml, SML, and Racket. In Section 4.3 we outline a practical method to prototype an implementation of handlers for a large set of such languages. A key reason for focusing on our Haskell library in this paper is that it is the only one that supports effect typing. Effect typing is crucial to the termination of our core calculus (Section 3). More importantly, it it is crucial for our notion of soundness, as it statically ensures that operations do not accidentally go unhandled. Anecdotally, we have observed that such static guarantees are important in practice: when we added effect typing to an early version of our Haskell library, it revealed a number of bugs in our test examples. The code for our effect handler libraries, examples, and benchmarks is available in the GitHub repository at: This repository also includes many other other examples. For instance, we have reimplemented Kiselyov and Shan s HANSEI DSL for probabilistic computation [22], Kiselyov s iteratees [21], and Gonzalez s Pipes library [14], all using handlers. Template Haskell and Quasiquotes Template Haskell [40] is a facility for compile-time meta programming in Haskell. It provides a data type for manipulating Haskell code as an abstract syntax tree. It also provides constructs for splicing chunks of Haskell together. Quasiquotes [28] extend Template Haskell splicing functionality with user-defined syntax. Each syntax extension (also known as quasiquoter) is associated with a name. To define syntax extension, ext, a library writer supplies a parser for ext expressions as a function that takes a string and returns a Haskell abstract syntax tree. To invoke the syntax extension, a programmer writes an expression e in quasiquote brackets [ext e ], a quasiquote. At compile-time, GHC runs the parser on e and splices in the resulting abstract syntax tree in place of the quasiquote brackets. 2.1 State and Handlers We introduce the primitives for abstract operations and handlers in our Haskell library through the example of global state. We define abstract operations for state with the following operation quasiquotes [operation Get s :: s ] [operation Put s :: s () ] which declare a Get s operation that takes no parameters and returns values of type s, and a Put s operation that takes a single parameter of type s and returns values of type (). In general an abstract operation declaration has the form [operation u 1... u l.op e 1... e m :: A 1... A n A ] where Op is the name of the operation, u 1,..., u l are universal type variables, e 1,..., e m are existential type variables, A 1,..., A n are parameter types, and A is the return type. (We will discuss the role of universal and existential type variables in Section 2.2.) The declarations above automatically derive wrappers get and put for actually invoking the operations. Ideally, we would like their types to be get :: Comp {Get s } s put :: s Comp {Put s } () where Comp ε a is the type of abstract computations that can perform abstract operations in the set ε and return a value of type a. But GHC does not have a built-in effect type-system, so we simulate one, encoding sets of operations as type class constraints. Thus, get and put actually have slightly more complicated types: get :: [handles h {Get s } ] Comp h s put :: [handles h {Put s } ] s Comp h () We can think of the type variable h as standing for a set of operations, an effect set ε. Membership of operation Op in ε is denoted by the quasiquotation [ handles h {Op } ] (which is desugared into a corresponding type class constraint). The reason we write handles instead of contains, and h instead of ε, is that h is more than just an effect set; it actually ranges over handlers for ε. Thus Comp h represents computations interpreted by handlers of type h, and the constraint [ handles h {Op } ] really means: handler h handles operation Op. (We will introduce the syntax for handlers shortly.) We define the type of abstract state computations as follows 2 : type SComp s a = h.([handles h {Get s } ], [handles h {Put s } ]) Comp h a For example: 2 We would ideally like to write [handles h {Get s, Put s } ] as a single constraint, but Template Haskell currently only allows us to generate one type class constraint per quasiquote.

3 comp :: SComp Int Int comp = do {x get; put (x + 1); y get; put (y + y); get } Because Haskell is lazy we still require notation for explicitly sequencing computations. We take advantage of the existing do notation, and Comp h is implemented as a certain kind of universal monad (see Section 4). We can provide many concrete interpretations of stateful computation, which is where handlers come in. First, we interpret state in the standard monadic way: 1 2 RunState s a :: s (a, s) 3 handles {Get s, Put s } where 4 Return x s (x, s) 5 Get k s k s s 6 Put s k k () s ] We describe the syntax line by line. Line 1 begins a handler quasiquote. Line 2 specifies the name, type parameters, and type signature of the handler. Notice that the type signature s (a, s) is that of the state monad. The type signature indicates that this handler takes one parameter of type s, which is threaded through the handler, and returns a result of type (a, s). Line 3 specifies the set of operations handled by the handler. Line 4 is a return clause. It expresses how to return a final value from a computation. In general, a return clause takes the form Return x y 1... y n e, where x binds the value returned by the computation and y 1,..., y n bind the handler parameters. Here, the final value is paired up with the single state parameter. Lines 5 and 6 are operation clauses. They express how to handle each operation. In general, an operation clause takes the form Op x 1... x m k y 1... y n e, where x 1,..., x m bind the operation parameters, k binds the continuation of the computation, and y 1,..., y n bind the handler parameters, here the single state parameter. The continuation k is a curried function which takes a return value followed by a sequence of handler parameters, and yields the interpretation of the rest of the computation. For Get, the return value is the current state, which is threaded through the rest of the computation. For Put s, the existing state is ignored, the return value is (), and the state parameter is updated to s. Analogously to abstract operation declarations, a handler declaration generates a convenient wrapper, whose name is derived from that of the handler by replacing the first letter with its lower case counterpart. runstate :: s SComp s a (a, s) *Main> runstate 1 comp (4, 4) If we do not need to read the final contents of the state, then we can give a simpler interpretation to state [36], using the type that a Haskell programmer might normally associate with a read-only state monad: EvalState s a :: s a handles {Get s, Put s } where Return x s x Get k s k s s Put s k k () s ] *Main> evalstate 1 comp 4 More interestingly, we can give other interpretations: LogState s a :: s (a, [s ]) handles {Get s, Put s } where Return x s (x, [ ]) Get k s k s s Put s k let (x, ss) = k () s in (x, s : ss) ] This handler logs the history of all writes to the state. For instance, *Main> logstate 1 comp (4, [2, 4]) 2.2 State and Open Handlers The three handlers of Section 2.1 are closed. They each handle Get and Put, but cannot interpret computations that might perform other operations. Thus they do not support modular instantiation. Open handlers extend closed handlers by automatically forwarding all operations that are not explicitly handled. For instance, the following defines a handler that forwards all operations other than Get and Put: forward h. OpenState s a :: s a handles {Get s, Put s } where Return x s return x Get k s k s s Put s k k () s ] The type variable h is an artefact of the Haskell implementation. It represents an abstract parent handler that will ultimately handle operations forwarded by OpenState. It is implicitly added as the first type argument to OpenState (yielding OpenState h s a) and Comp h is implicitly applied to the return type (yielding Comp h a). Any operations other than Get or Put will be automatically forwarded to h. To illustrate the composability of open handlers, we return to the logging example. In Section 2.1, we demonstrated how to log Put operations using a special handler. We now factor the logging in such a way that we can refine any abstract stateful computation into an equivalent abstract computation that also performs logging, such that both logging and state can be subsequently interpreted in arbitrary ways using suitable handlers. First we define a new operation for logging each Put: [operation LogPut s :: s () ] Now we can define an open handler that inserts a LogPut operation before every Put operation in the original computation, but otherwise leaves it unchanged: forward h handles {Put s, LogPut s }. PutLogger s a :: a handles {Put s } where Put s k do {logput s; put s; k ()} ] For instance, the computation putlogger comp is equivalent to: do {x get; logput (x + 1); put (x + 1); y get; logput (y + y); put (y + y); get } The constraint (h handles {Put s, LogPut s }) asserts that the parent handler h must also handle the Put s and LogPut s operations 3. To obtain the original behaviour of LogState, we can define the following open handler: forward h. LogPutReturner s a :: (a, [s ]) handles {LogPut s } where Return x return (x, [ ]) LogPut s k do (x, ss) k (); return (x, s : ss) ] 3 Under the hood this aids GHC type inference.

4 and compose several handlers together: statewithlog :: s SComp s a (a, [s ]) statewithlog s comp = (handlepure logputreturner openstate s putlogger) comp where HandlePure is a canonical top-level closed handler: HandlePure a :: a handles { } where Return x x ] which interprets a pure computation as a value of type a. An alternative interpretation of logging is to output logging messages as they arrive: forward h handles {Io }.(Show s) LogPutPrinter s a :: a handles {LogPut s } where LogPut s k do io (putstrln ("Put: " + show s)); k () ] Now we can plug everything together: stateprintlog :: Show s s SComp s a IO a stateprintlog s comp = (handleio logputprinter openstate s putlogger) comp where HandleIO is another top-level closed handler for performing arbitrary operations in the IO monad with the Io operation: [operation a.io :: IO a a ] HandleIO a :: IO a handles {Io } where Io m k do {x m; k x } ] The universal quantifier in the Io operation declaration indicates that it must be handled polymorphically in a. This is in contrast to the declaration of Get, for instance: [operation Get s :: s ] where the type parameter s is existential, in the sense that for any handler that handles Get, there must exist a fixed type for s. Correspondingly, in any given abstract computation, Io can be used at arbitrary types a whereas Get must be used at a fixed type s. Comparing the outputs on our sample computation we obtain: *Main> statewithlog 1 comp (4, [2, 4]) *Main> stateprintlog 1 comp Put: 2 Put: 4 4 The pattern of precomposing one closed top-level handler with a sequence of open handlers is common when using our library. The order in which open handlers are composed may or may not change the semantics. For instance, if we were to swap the order of openstate s and putlogger in stateprintlog then all of the Put operations would be handled before any PutLog operations could be generated, so no logging information would ever be output. On the other hand, if we were to swap the order of logputprinter and openstate s then the semantics would be unchanged as their actions are orthogonal. Open handlers allow us to handle a subset of the effects in an abstract computation, thus supporting modular instantiation. The next three subsections present more involved examples, demonstrating the interaction of user-defined effects with various Haskell features. 2.3 Choice and Failure Consider abstract operations Choose and Failure: [operation a.choose :: a a a ] [operation a.failure :: a ] The idea is that Choose should select one of its two arguments of type a, and Failure just aborts. Abstract choice computations are interesting because they admit a range of useful interpretations. Archetypal handlers which we consider include those that enumerate all choices (AllResults below) and random sampling (RandomResult below). The former is notable as it takes full advantage of the ability for an operation clause to invoke the continuation more than once. The type of abstract computations over Choose and Failure is: type CF a = h.([handles h {Choose } ], [handles h {Failure } ]) Comp h a As a simple example, consider the following program: data Toss = Heads Tails deriving Show drunktoss :: CF Toss drunktoss = do {caught choose True False; if caught then choose Heads Tails else failure } drunktosses :: Int CF [Toss ] drunktosses n = replicatem n drunktoss The abstract computation drunktoss simulates a drunk performing one coin toss. If the drunk catches the coin then the result of tossing the coin (Heads or Tails) is returned. If the coin falls into the gutter then no result is returned. The drunktosses function repeats the process the specified number of times. We can write a handler that returns all possible results of a CF computation as a list, providing a model of non-determinism. AllResults a :: [a ] handles {Choose, Failure } where Return x [x ] Choose x y k k x + k y Failure k [ ] ] This is the first handler we have seen that uses the continuation non-linearly. The Choose operation is handled by concatenating the results of invoking the continuation with each alternative. The Failure operation is handled by returning the empty list and ignoring the continuation. For example: *Main> allresults (drunkcoins 2) [[Heads, Heads ], [Heads, Tails ], [Tails, Heads ], [Tails, Tails ]] Rather than returning all of the results of a CF computation, we might wish to sample a single result at random. In order to keep the implementation of randomness abstract, let us declare a new operation for generating random numbers. [operation Rand :: Double ] We first give a handler for Choose alone. forward h handles {Rand }. RandomResult a :: a handles {Choose } where Choose x y k do {r rand; k (if r < 0.5 then x else y)} ] Unlike in the AllResults handler, the Choose operation is handled by supplying one of the arguments to the continuation at random. We can implement randomness using the IO monad. HandleRandom a :: IO a handles {Rand } where Rand k do {r getstdrandom random; k r } ] Let us now define another open handler for handling Failure, interpreting the result of a possibly failing computation with a Maybe type.

6 wcstring :: String IO () wcstring s = let (c, w, l) = handlepure (stringreader s wc) in putstrln $ (show l) + " " + (show w) + " " + (show c) Here is a version of wc that uses standard input: wcstdin :: IO () wcstdin = do (c, w, l) handleio (stdinreader wc) putstrln $ (show l) + " " + (show w) + " " + (show c) In practice, one might define other handlers in order to support file input, network input, or different forms of buffering. 2.5 Tail The tail program takes an argument n and prints the last n lines of a text file. In order to implement the functionality of tail, we make use of readline as well as two additional abstract operations: the first to record a line, and the second to print all recorded lines. [operation SaveLine :: String () ] [operation PrintAll :: () ] With these two operations, implementing an abstract tail computation tailcomp is straightforward. tailcomp :: ([handles h {ReadChar } ], [handles h {Finished } ], [handles h {SaveLine } ], [handles h {PrintAll } ]) Comp h () tailcomp = do s readline; saveline s b finished; if b then printall else tailcomp We now just need to handle the SaveLine and ReadLine operations. A naive handler might store all saved lines in memory, and print the last n as required. In practice, a more efficient implementation might store only the last n lines, using a circular array, say. 2.6 Pipes and Shallow Handlers The behaviour of handlers we have described thus far is such that the continuation of an operation is handled with the current handler (though the parameters passed to the continuation may differ from the current parameters). Another possible behaviour is for the continuation to return an unhandled computation, which must then be handled explicitly. We call such handlers shallow handlers because each handler only handles one step of a computation, in contrast to Plotkin and Pretnar s deep handlers. Shallow handlers are to deep handlers as case analysis is to a fold on an algebraic data type. Shallow handlers sometimes lead to slightly longer code. For example, the EvalState handler from Section 2.1 becomes: [shallowhandler EvalStateShallow s a :: s a handles {Get s, Put s } where Return x s x Get k s evalstateshallow (k s) s Put s k evalstateshallow (k ()) s ] The need to call the handler recursively in most clauses is characteristic of the style of program one writes with shallow handlers. In some situations, it is helpful to have access to the unhandled result of the continuation. Consider pipes as exemplified by Gonzalez s pipes library [14]. A pipe is a data structure used to represent composable producers and consumers of data. A consumer can await data and a producer can yield data. A pipe is both a consumer and a producer. It is straightforward to provide such an abstraction with the following operations 5 : 5 These operations have exactly the same signatures as Get and Put, but their intended interpretation is different. For instance, yield x; yield y is in no way equivalent to yield y. [operation Await s :: s ] [operation Yield s :: s () ] To define a plumbing operator that combines a compatible consumer and producer we write two handlers: one handles the downstream consumer and keeps a suspended producer to resume when needed, the other handles the upstream producer and keeps a suspended consumer. These two handlers are straightforward to write using shallow handlers: [shallowhandler forward h.down s a :: Comp (Up h a) a a handles {Await s } where Return x return x Await k prod up k prod ] [shallowhandler forward h.up s a :: (s Comp (Down h a) a) a handles {Yield s } where Yield s k cons down (k ()) (cons s) ] However, transforming these handlers into deep handlers requires some ingenuity. Indeed, we need to work with continuations that are fully handled and we cannot keep the simple mutually recursive structure of the two handlers. Instead, we introduce two mutually recursive type definitions data Prod s r = Prod (() Cons s r r) data Cons s r = Cons (s Prod s r r) which we use to encode the suspended partner of each computation forward h.down s a :: Prod s (Comp h a) a handles {Await s } where Return x return x Await k (Prod prod) prod () (Cons k) ] forward h.up s a :: Cons s (Comp h a) a handles {Yield s } where Return x return x Yield s k (Cons cons) cons s (Prod k) ] resulting in a more complex program. We believe both deep and shallow handlers are useful. For clarity of presentation, we focus on deep handlers in the rest of this paper. In Section 3.4 and Section 4.2 we outline how shallow handlers differ from the main presentation. 2.7 Other Perspectives In this paper we primarily treat handlers as a flexible tool for interpreting abstract effectful computations. Before we proceed with the rest of the paper we highlight some alternative perspectives on what handlers are. Generalised exception handlers. Benton and Kennedy [3] introduced the idea of adding a return continuation to exception handlers. Their return continuation corresponds exactly to the return clause of an effect handler. Effect handler operation clauses generalise exception handler clauses by adding a continuation argument, providing support for arbitrary effects. An operation clause that ignores its continuation argument behaves like a standard exception handler clause. Taming delimited continuations. A handler invocation delimits the start of a continuation. Each operation clause captures the continuation of the computation currently being handled, that is, the continuation up to the invocation point of the handler. Effect handlers modularise delimited continuations by capturing particular patterns of use. As Andrej Bauer, the co-creator of the Eff [2] lan-

7 (values) A, B ::= 1 A 1 A 2 0 A 1 + A 2 U E C (computations) C ::= F A A C C 1 & C 2 (effect signatures) E ::= {op : A B} E (handlers) R ::= A E E C (environments) Γ ::= x 1 : A 1,..., x n : A n Figure 1. Types and Effects of λ eff (values) V, W ::= x () (V 1, V 2) inj i V {M} (computations) M, N ::= split(v, x 1.x 2.M) case 0(V ) case(v, x 1.M 1, x 2.M 2) V! return V let x M in N λx.m M V M 1, M 2 prj i M op V (λx.m) handle M with H (handlers) H ::= {return x M} H {op p k N} Figure 2. Syntax of λ eff Terms guage puts it (personal communication, 2012): effects + handlers : delimited continuations = while : goto Folds over free monads. As we shall see in Section 4, we can define an algebraic data type for a collection of operations, and a handler is exactly a fold (otherwise known as catamorphism) over that data type. 3. The λ eff -calculus In this section, we present a small-step operational semantics and a sound type and effect system for λ eff, a higher-order calculus of effect handlers. Following related work on effect operations [19], effect handlers [36], and monadic reflection [11], which takes Levy s call-by-push-value [24] as the underlying paradigm, we extend Levy s calculus with effect operations and effect handlers. For our purposes, the important features of call-by-push-value are that it makes an explicit distinction between values and computations, and that thunks are first-class objects distinct from functions. 3.1 Syntax and Static Semantics The types and effects of λ eff are given in Figure 1, the terms are given in Figure 2, and the typing rules are given in Figure 3. In all figures, the interesting parts are highlighted in grey. The unhighlighted parts are standard. Call-by-push-value makes a syntactic distinction between values and computations. Only value terms may be passed to functions, and only computation terms may compute. Value types (Figure 1) comprise the value unit type (1), value products (A 1 A 2), the empty type (0), sums (A 1 + A 2), and thunks (U EC). The latter is the type of suspended computations. The effect signature E describes the effects that such computations are allowed to cause. Computation types comprise value-returning computations (F A), functions (A C), the computation unit type ( ), and computation product types (C 1 & C 2). Call-by-push-value includes two kinds of products: computation products, which are eliminated by projection, and value products, which are eliminated by binding. An effect signature is a mapping from operations to pairs of value types, written as a set of type assignments. Each type assignment op : A B, specifies the parameter type A and return type B of operation op. A handler type A E E C has a input value type A, output computation type C, input effect signature E, and output effect signature E. A handler of this type handles value-returning computations of type F A that can only perform operations in E. The body of the handler itself may only perform operations in E, and its computation type is C. Type environments are standard. Value terms (Figure 2) include variables and value introduction forms. We write {M} for the thunk that represents the suspended computation M as a value. All elimination occurs in computation terms, as is standard for call-by-push-value. We write split(v, x 1.x 2.M) for the elimination form for value products, which binds the components of the product value V to the variables x 1 and x 2 in the computation M. We write M 1, M 2 for a computation pair and prj i M for the i-th projection of M. We write V! for the computation that forces the thunk V, that is, runs the computation suspended in V. A lambda-abstraction λx.m is not a value, so must be suspended to be passed as an argument. Function application, products, and projections are standard. In λ eff operation applications are in continuation-passing-style. An operation application op V (λx.m) takes a parameter V and a continuation λx.m. The intuition is that the operation op is applied to the parameter V, returning a value that is bound to x in the continuation computation M. We restrict the continuation to be a lambda abstraction in order to simplify the operational semantics. While programming with effects, it is more convenient to work with direct-style operation application. Direct-style application can be defined in terms of continuation-passing-style application: ôp V = op V (λx.return x), and vice versa: op V (λx.m) = let x ôp V in M. Plotkin and Power call the function λx.ôp x underlying a direct-style application the generic effect of op [35]. A handled computation handle M with H runs the computation M with the handler H. A handler H consists of a return clause return x M, and a set of operation clauses of the form op p k N. The return clause return x M specifies how to handle a return value. The returned value is bound to x in M. Each operation clause op p k N specifies how to handle applications of the distinct operation name op. The parameter is bound to p and the continuation is bound to k in N. The body of the continuation continues to be handled by the same handler. The typing rules are given in Figure 3. The computation typing judgement Γ E M : C states that in type environment Γ the computation M has type C and effect signature E. Only operations in the current effect signature can be applied. Handling a computation changes the current effect signature to the output effect signature of the handler. The effect signature and type of the handled computation must match up exactly with the input type and effect signature of the handler. In the handler typing judgement Γ H : R, all clauses must have the same output type and effect signature. The input type is determined by the return clause. The effect annotation on the thunked continuation parameter k in an operation clause op p k N is annotated with the output effect rather than the input effect. The reason for this is that when handling an operation, the handler is automatically wrapped around the continuation. Syntactic Sugar For convenience, we define syntactic sugar for projecting out the return clause and operation clauses of a handler. For any handler we write {return x M} {op i p k N i} i H return λx.m H op i λp i k i.n i

9 derivations shows preservation: if Γ E M : C and M M then Γ E M : C. 3.3 Open Handlers Our presentation of λ eff gives an operational account of closed handlers. We can adapt λ eff to support open handlers by making two small changes. The typing rule for handlers becomes: E = E {op i : A i B i} i H = {return x M} {op i p k N i} i [Γ, p : A i, k : U E (B i C) E N i : C] i Γ, x : A E M : C Γ H : A E E C The only change to the original rule is that the input effects are now E E instead of just E, where E E is the extension of E by E (where any clashes are resolved in favour of E). The handle.op-rule is refined by extending the meaning of H op, such that it is defined as before for operations that are explicitly handled by H, but is also defined as λp k.op p(λx.k x) for any other operation op. This means that any operation that is not explicitly handled gets forwarded. In our simply-typed formalism, it is straightforward to translate any program that uses open handlers into an equivalent program that uses closed handlers. As any open handler handles a bounded number of operations, we can simply write down all of the implicit forwarding clauses explicitly. In practice, it seems desirable to offer both open and closed handlers, as in our Haskell library. To take full advantage of open handlers in a typed language, one inevitably wants to add some kind of effect polymorphism. Indeed, our Haskell implementation provides effect polymorphism, encoded using type classes. We believe that effect polymorphism can be supported more smoothly using row polymorphism. We briefly outline one path to supporting row polymorphism. The open handler rule from above can be rewritten as follows: E = {op i : A i B i} i E f E = E E f H = {return x M} {op i p k N i} i [Γ, p : A i, k : U E (B i C) E N i : C] i Γ, x : A E M : C Γ H : A E E C The key difference is that this version of the rule uses disjoint union in place of extension, explicitly naming the collection of forwarded effects. One can now instantiate the meta variable E f with a row variable. We would likely also wish to support polymorphism over E. This is not difficult to achieve using a Remy-style [37] account of row typing if we insist that E only include operations in {op i } i. We leave a full investigation of effect polymorphism for handlers to future work. 3.4 Shallow Handlers Our presentation of λ eff gives an operational account of deep handlers. In order to model shallow handlers we can make two small changes. The typing rule for handlers becomes: E = {op i : A i B i} i H = {return x M} {op i p k N i} i [Γ, p : A i, k : U E(B i F A) E N i : C] i Γ, x : A E M : C Γ H : A E E C The only changes with respect to the original rule are to the types of the continuations, which now yield F A computations under the input effect signature E, rather than C computations under the output effect signature E. The handle.op-rule is replaced by the shallow-handle.op-rule: (shallow -handle.op) H op = λp k.n x / FV (H) handle op V (λx.m) with H N[V/p, {λx.m}/k] which does not wrap the handler around the continuation. Of course, without recursion shallow handlers are rather weak. 4. Implementation Any signature of operations can be viewed as a free algebra and represented as a functor. Every such functor gives rise to a free monad (Swierstra [43] gives a clear account of free monads for functional programmers). This yields a systematic way of building a monad to represent computations over a signature of operations. We use our standard state example to illustrate. Concretely we can define the free monad over state as follows: data FreeState s a = Ret a Get () (s FreeState s a) Put s (() FreeState s a) instance Monad (FreeState s) where return = Ret Ret v >= f = f v Get () k >= f = Get () (λx k x >= f ) Put s k >= f = Put s (λx k x >= f ) The type FreeState s a is a particular instance of a free monad. It can be viewed as a computation tree. The leaves are labelled with Ret v and the nodes are labelled with Get () and Put s. There is one edge for each possible return value supplied to the continuation of Get and Put a possibly infinite number for Get depending on the type of the state, and just one for Put. The bind operation performs a kind of substitution. To compute c >= f, the tree f v is grafted onto each leaf Ret v of c. The generic free monad construction can be defined as follows: data Free f a = Ret a Do (f (Free f a)) instance Functor f Monad (Free f ) where return = Ret Ret v >= f = f v Do op >= f = Do (fmap ( >=f ) op) and we can instantiate it with state as follows: data StateFunctor s a = GetF () (s a) PutF s (() a) deriving Functor where FreeState s is isomorphic to Free (StateFunctor s). A handler for state is now simply a unary function whose argument has type Free (StateFunctor s). For instance: stateh :: Free (StateFunctor s) a (s a) stateh (Ret x) = λs x stateh (Do (GetF () k)) = λs stateh (k s) s stateh (Do (PutF s k)) = λ stateh (k ()) s interprets a stateful computation as a function of type s a. A limitation of the above free monad construction is that it is closed in that it can only handle operations in the signature. A key feature of our library is support for open handlers that handle a fixed set of operations in a specified way, and forward any other operations to be handled by an outer handler. To encode openness in GHC we take advantage of type classes and type families. The code for open free monads is given in Figure 5. We split the type of each operation into two parts: a type declaration that defines the parameters to the operation, and a type family instance that defines the return type of the operation. For instance: [operation Put s :: s () ] generates:

10 data Put (e :: ) (u :: ) where Put :: s Put s () type instance Return (Put s ()) = () The first type argument e encodes the existential type arguments of an operation, while the second type argument u encodes the universal type arguments of an operation. In the case of Put there is a single existential type argument s and no universal arguments. Using GADTs we can encode multiple arguments as tuples. Handler types are generated similarly. Lines 1 2 of Figure 5 declare type families for operation return types and handler result types. Lines 3 6 define a ternary type class (h Handles op) e. Each instance of this class defines the clause of handler h that handles operation op with existential type arguments bound to e. Of course, we do not supply the universal arguments, as the clause should be polymorphic in them. The functional dependency h op a asserts that type a must be uniquely determined by types h and op. This is crucial for correctly implementing open handlers as we discuss further in Section 4.1. The handles quasiquoter generates type class constraints on the Handles type class. Lines 7 14 define the monad Comp h, which is simply a free monad over the functor defined by those operations op that are handled by h (i.e. such that (h Handles op) e is defined for some type e). Lines define the auxiliary doop function, which realises an operation as an abstract computation of the appropriate type. The operation quasiquoter uses doop to automatically generate a function for each operation. For instance, the above declarations for Get and Put generate the following functions: get :: (h Handles Get) s Comp h s get = doop Get put :: (h Handles Put) s s Comp h () put s = doop (Put s) Finally, Lines define the one remaining ingredient for the core library, the handle function, which takes a computation, a return clause, and a handler, and returns the result of handling the computation. We supply the return clause independently from the type class mechanism in order to simplify the implementation. The handler is automatically applied to the result of the continuation as specified in the operational semantics. This behaviour contrasts with the closed free monad code presented at the beginning of this subsection, which instead uses explicit recursion as with the shallow handlers for state and pipes. We are making essential use of the type class mechanism. It is instructive to read the type of handle as taking a return clause, a list of operation clauses, one for each op such that (h Handles op) e for some e, and returning a result. Thus the second argument of type h, as well as providing parameters to the handler, also, albeit indirectly, encodes the list of operation clauses. The handler quasiquoter automatically generates a convenient wrapper meaning that programmers need never directly manipulate the constructor for a handler type just as automatically generated operation wrappers mean that they need never directly manipulate the constructor for an operation type. Limitations Our Haskell implementation of handlers has several limitations. First, because handlers are encoded as type classes and type classes are not first-class, neither are handlers. Second, because we abstract over handlers in order to simulate effect typing the types of the operation wrappers are more complex than necessary. Third, because we explicitly mention a parent handler in the type of open handlers, the order in which open handlers are composed can leak into types (this is not as bad as with monad transformers, as lifting is never required, but it is still undesirable). All of these limitations arise from attempting to encode handlers in Haskell. None is inherent to handlers. We believe that a row- 1 type family Return (opapp :: ) :: 2 type family Result (h :: ) :: 3 class ((h :: ) Handles (op :: j k )) (e :: j ) h op e 4 where 5 clause :: op e u 6 (Return (op e u) h Result h) h Result h 7 data Comp h a where 8 Ret :: a Comp h a 9 Do :: (h Handles op) e 10 op e u (Return (op e u) Comp h a) Comp h a 11 instance Monad (Comp h) where 12 return = Ret 13 Ret v >= f = f v 14 Do op k >= f = Do op (λx k x >= f ) 15 doop :: (h Handles op) e 16 op e u Comp h (Return (op e u)) 17 doop op = Do op return 18 handle :: Comp h a (a h Result h) h Result h 19 handle (Ret v) r h = r v h 20 handle (Do op k) r h = 21 clause op (λv h handle (k v) r h ) h Figure 5. Free Monad Implementation 1 type family Return (opapp :: ) :: 2 type family Result (h :: ) :: 3 class ((h :: ) Handles (op :: j k )) (e :: j ) h op e 4 where 5 clause :: op e u (Return (op e u) h Result h) 6 h Result h 7 newtype Comp h a = 8 Comp {handle :: (a h Result h) h Result h } 9 instance Monad (Comp h) where 10 return v = Comp (λk k v) 11 Comp c >= f = Comp (λk c (λx handle (f x) k)) 12 doop :: (h Handles op) e 13 op e u Comp h (Return (op e u)) 14 doop op = Comp (λk h clause op k h) Figure 6. Continuation Monad Implementation based effect type system along the lines of Leroy and Pesaux [23], Blume et al [5], or Lindley and Cheney [27] would provide a cleaner design. The Codensity Monad It is well known that free monad computations can be optimised by composing with the codensity monad, which is essentially the continuation monad over a polymorphic return type [45]. The Continuation Monad We can in fact do even better by using the continuation monad directly, meaning that the Ret and Do constructors disappear completely. The continuation monad code is given in Figure 6. The difference from the free monad code begins on Line 7. The type constructor Comp h is exactly that of the continuation monad with return type h Result h. We choose not to factor through the continuation monad defined in the standard library as doing so hurts performance. The handle function is now exactly the deconstructor for Comp, while the doop function is just Comp clause. We explicitly η-expand doop because GHC is unable to optimise the pointless version. 4.1 Open Handlers and Forwarding The key trick for implementing forwarding is to parameterise a handler H by its parent handler h. Without this parameter we would

11 have no way of describing the operations that are handled by both H and h. Now we can define the following type class instance: instance (h Handles op) e (H h Handles op) e where clause op k h = doop op >= (λx k x h) The handler quasiquoter generates this boilerplate automatically for open handlers. The functional dependency (H h) op e is crucial here. Without it GHC would be unable to resolve the clause function. For instance, consider the OpenState handler. This must select from the following instances for Get: instance (OpenState h s a Handles Get) s where clause Get k (OpenState s) = k s (OpenState s) instance (h Handles op) t (OpenState h s a Handles op) t where clause op k h = doop op >= (λx k x h) Without the functional dependency the latter is chosen. This is because GHC tries to ensure that the same version of clause is used for Get t for any t, and the former is only valid if s is equal to t. The functional dependency asserts that t must be equal to s. Because the type variable t does not appear in either of the types OpenState h s a or op, and there is a functional dependency which states that OpenState h s a and op uniquely determine e, GHC s default type inference gives up. Enabling the UndecidableInstances language option fixes this. We believe that our basic use of UndecidableInstances is well-founded (and decidable!), because of the type class constraint (h Handles op) t which implies that h and op already uniquely determine t. 4.2 Shallow Handlers It is relatively straightforward to adapt our free monad implementation to implement shallow handlers. The key change is to the type of the continuation argument of the clause function which must return a computation. It seems less clear how to adapt the continuation monad implementation. 4.3 Delimited Continuations We now sketch an implementation of (open) effect handlers in terms of delimited continuations [8, 9]. These ideas underlie our OCaml, SML, and Racket implementations. A variety of different delimited continuation operators are covered in the literature. Shan has recently shown that the four basic choices are straightforwardly inter-definable [39] 6. We choose to describe our implementation in terms of a minor variant of Danvy and Filinski s shift and reset operators [8] called shift0 and reset0. The behaviour of shift0 and reset0 can be concisely summarised through the following reduction rule: reset0 (E[shift0 (λk.m)]) M[(λx.reset0 (E[x]))/k] where E ranges over call-by-value evaluation contexts. The reset0 operator delimits the start of a continuation, and the shift0 operator captures the continuation up to the nearest enclosing reset0. Crucially, the captured continuation is wrapped in a further reset0. It is instructive to compare the above rule with the handle.op-rule, where handle with H plays a similar role to reset0. The implementations rely on the following key ingredients: A global (or thread-local) variable keeps a stack of handlers in the current dynamic scope. Each handler includes a map from the handled operations to the corresponding operation clause. 6 These encodings do not preserve memory behaviour, so can sometimes introduce memory leaks. To handle an effectful computation handle M with H: The handler H is added to the top of the stack. We invoke reset0 (H return M). To apply an operation (in direct style) ôp p: 1. We invoke shift0 to capture the continuation k up to (but excluding) the next operation handler. 2. The top-most handler H is popped from the stack. 3. We let k = λx.push H; reset0 (k x), where push H pushes H back onto the stack. 4. The clause corresponding to the operation, that is H op, is applied to the parameter p and the continuation k. 5. If there is no clause corresponding to this operation, it will be forwarded by the handler. If no other handlers enclose the operation, an exception is raised. To support shallow handlers, one replaces shift0 and reset0 with control0 and prompt0, which behave like shift0 and reset0, except no prompt0 is wrapped around the continuation: prompt0 (E[control0 (λk.m)]) M[(λx.E[x])/k] 4.4 Dynamic and Static Operations Our Haskell implementation uses one static type per operation. A program execution cannot dynamically create a new operation. Because they do not provide effect typing, our other implementations do support dynamic operations, which can be created, closed upon and garbage collected. This makes some programs easier to write. For example, references can be represented as pairs of dynamically generated Put and Get operations. With only static operations, one has to parameterise Put and Get by some representation of a reference, and explicitly manage all of the state in a single handler. Static effect typing for dynamic operations presents challenges: Writing an effect type system for dynamic operations involves some form of dependent types, as operations are now first-class objects of the language. Dynamic operations are difficult to implement as efficiently as static operations. In particular, it is not clear how to use the type system to pass only the relevant effects to each scope. 5. Performance Evaluation To evaluate the performance of our Haskell library, we implemented a number of micro-benchmarks, comparing handler code against monadic code that makes use of existing libraries. The code for the micro-benchmarks can be found in the GitHub repository at: Detailed performance results can be found in Appendix A. Our primary goal was to check that the handler abstraction does not cripple performance. We rely on GHC to optimise away many of the abstractions we introduce. In the future we envisage building handlers into the core of a programming language. We might reasonably hope to do significantly better than in the librarybased approach by tailoring optimisations to be aware of handlers. The results confirm that the Haskell library performs adequately. The performance of the continuation monad implementation of handlers is typically no worse than around two thirds that of baseline code. In some cases the continuation monad implementation actually outperforms existing implementations. The continuation monad implementation always outperforms the codensity monad implementation (sometimes by more than an order of magnitude), which always outperforms the free monad implementation. Usually standard handlers outperform shallow handlers,

12 pipes being an exception, where for large numbers of nested subpipes shallow handlers outperform even the continuation monad implementation of standard handlers. 6. Related Work Algebraic Effects and Effect Handlers Effect operations were pioneered by Plotkin and Power [35], leading to an algebraic account of computational effects [34] and their combination [15]. Effect handlers were added to the theory in order to support exception handling [36]. Recent work incorporates additional computational effects within the algebraic framework, for example, local state [41], and applies the algebraic theory of effects to new problem domains, such as effect-dependent program transformations [19], and logical-relations arguments [20]. While mostly denotational in nature, operational accounts of algebraic effects (without handlers) do exist. Plotkin and Power [33] gave operational semantics to algebraic effects in a call-by-value setting, and Johann et al. [32] gave operational semantics to algebraic effects in a call-by-name setting. Effect Handler Implementations Bauer and Pretnar s effectful strict statically-typed language Eff [2] has built-in support for algebraic effects and effect handlers. Like our ML implementations, it lacks an effect type system. Eff implements dynamic generation of new operations and effects, which we only consider statically. Visscher has implemented the effects library [44] for Haskell inspired by Eff. The core idea is to layer continuation monads in the style of Filinski [10], using Haskell type classes to automatically infer lifting between layers. McBride s language Frank [29] is similar to Eff, but with an effect system along the lines of ours. It supports only shallow handlers and employs a novel form of effect polymorphism which elides effect variables entirely. Brady [6] has implemented an effect handlers library for the dependently-typed language Idris. It takes advantage of dependent types for resource tracking. The current design has some limitations compared with the other handler implementations. In particular, the composition of other effects with non-determinism is not well-behaved. Monadic Reflection and Layered Monads Filinski s work on monadic reflection and layered monads is closely related to effect handlers [11]. Monadic reflection supports a similar style of composing effects. The key difference is that monadic reflection interprets monadic computations in terms of other monadic computations, rather than abstracting over and interpreting operations. Filinski s system is nominal (an effect is the name of a monad), whereas ours is structural (an effect is a collections of operations). Monad Transformers and Inferred Lifting Jaskelioff and Moggi [17] develop the theory of monad transformers and lifting of effect operations. Jaskelioff s Monatron [16] is a monad transformer library based on this development. Schrijvers and Oliveira [38] infer lifting in Haskell using a zipper structure at the level of type classes to traverse the monad transformer stack. Swamy et al. [42] add support for monads in ML, inferring not only where and how to lift operations, but also where to insert return and bind statements. In both approaches, once the required monad transformers have been defined, the desired lifting is inferred automatically. 7. Conclusion Algebraic effects and handlers provide a promising approach for supporting effectful computations in functional languages. By offering a new form of modularity, they create possibilities for library design and reusability that are just beginning to emerge. This paper shows that implementing these constructs is within the reach of current compiler technology. Acknowledgments The λ eff calculus stemmed from discussions of the first author with Andrej Bauer and Matija Pretnar in Ljubljana and Swansea. The authors would like to thank Stevan Andjelkovic, Danel Ahman, Bob Atkey, Andrej Bauer, Brian Campbell, James Cheney, Derek Dreyer, Andrzej Filinski, Ben Kavanagh, Neel Krishnaswami, Conor McBride, James McKinna, Gordon Plotkin, Matija Pretnar, Alex Simpson, Sam Staton, Phil Wadler, and the POPL 2013, PLDI 2013, and ICFP 2013 referees, for useful conversations, comments and suggestions. We are grateful to Gabriel Gonzalez for pointing out a flaw in the pipes benchmarks in an earlier draft of this paper. The type system originated from a visit by the first author to Andrej Bauer and Matija Pretnar in Ljubljana, supported by the Laboratory for Foundations of Computer Science. This work was supported by a Google Research Award, EPSRC grants EP/J014591/1 and EP/H005633/1, a SICSA studentship, an Edinburgh University Informatics School studentship, and an Isaac Newton Trust starter grant. References [1] Z. M. Ariola, H. Herbelin, and A. Sabry. A type-theoretic foundation of delimited continuations. Higher-Order and Symbolic Computation, 22(3): , [2] A. Bauer and M. Pretnar. Programming with algebraic effects and handlers. CoRR, abs/ , [3] N. Benton and A. Kennedy. Exceptional syntax. J. Funct. Program., 11(4): , [4] N. Benton, J. Hughes, and E. Moggi. Monads and effects. In APPSEM Springer-Verlag, [5] M. Blume, U. A. Acar, and W. Chae. Exception handlers as extensible cases. In APLAS. Springer-Verlag, [6] E. Brady. Programming and reasoning with algebraic effects and dependent types. In ICFP. ACM, [7] B. C. d. S. Oliveira, T. Schrijvers, and W. R. Cook. MRI: Modular reasoning about interference in incremental programming. J. Funct. Program., 22(6): , [8] O. Danvy and A. Filinski. Abstracting control. In LFP. ACM, [9] M. Felleisen. The theory and practice of first-class prompts. In POPL. ACM, [10] A. Filinski. Representing layered monads. In POPL. ACM, [11] A. Filinski. Monads in action. In POPL. ACM, [12] A. Gill. The mtl package (2.1.2), [13] G. Gonzalez. pipes-2.5: Faster and slimmer, pipes-25-faster-and-slimmer.html. [14] G. Gonzalez. The pipes package (3.2.0), [15] M. Hyland, G. D. Plotkin, and J. Power. Combining effects: Sum and tensor. Theoret. Comput. Sci., pages 70 99, [16] M. Jaskelioff. Monatron: An extensible monad transformer library. In IFL. Springer-Verlag, [17] M. Jaskelioff and E. Moggi. Monad transformers as monoid transformers. Theoret. Comput. Sci., 411(51 52), [18] M. P. Jones. Functional programming with overloading and higherorder polymorphism. In Advanced Functional Programming, [19] O. Kammar and G. D. Plotkin. Algebraic foundations for effectdependent optimisations. In POPL. ACM, [20] S. Katsumata. Relating computational effects by -lifting. Inf. Comput., 222, [21] O. Kiselyov. Iteratees. In FLOPS. Springer-Verlag, [22] O. Kiselyov and C.-c. Shan. Embedded probabilistic programming. In DSL. Springer-Verlag, 2009.

13 [23] X. Leroy and F. Pessaux. Type-based analysis of uncaught exceptions. ACM Trans. Program. Lang. Syst., pages , [24] P. B. Levy. Call-By-Push-Value: A Functional/Imperative Synthesis, volume 2 of Semantics Structures in Computation. Springer, [25] S. Liang, P. Hudak, and M. P. Jones. Monad transformers and modular interpreters. In POPL. ACM, [26] S. Lindley. Extensional rewriting with sums. In TLCA. Springer- Verlag, [27] S. Lindley and J. Cheney. Row-based effect types for database integration. In TLDI. ACM, [28] G. Mainland. Why it s nice to be quoted: quasiquoting for Haskell. In Haskell. ACM, [29] C. McBride. Frank (0.3), [30] E. Moggi. Computational lambda-calculus and monads. In LICS. IEEE Computer Society, [31] B. O Sullivan. The criterion package ( ), [32] A. S. Patricia Johann and J. Voigtländer. A generic operational metatheory for algebraic effects. In LICS. IEEE Computer Society, [33] G. D. Plotkin and J. Power. Adequacy for algebraic effects. In FoSSaCS. Springer-Verlag, [34] G. D. Plotkin and J. Power. Notions of computation determine monads. In FoSSaCS. Springer-Verlag, [35] G. D. Plotkin and J. Power. Algebraic operations and generic effects. Appl. Categ. Structures, 11(1):69 94, [36] G. D. Plotkin and M. Pretnar. Handlers of algebraic effects. In ESOP. Springer-Verlag, [37] D. Rémy. Type inference for records in a natural extension of ML. In C. A. Gunter and J. C. Mitchell, editors, Theoretical Aspects Of Object-Oriented Programming. Types, Semantics and Language Design. MIT Press, [38] T. Schrijvers and B. C. d. S. Oliveira. Monads, zippers and views: virtualizing the monad stack. In ICFP. ACM, [39] C.-c. Shan. A static simulation of dynamic delimited control. Higher- Order and Symbolic Computation, 20(4): , [40] T. Sheard and S. L. P. Jones. Template meta-programming for Haskell. SIGPLAN Notices, 37(12):60 75, [41] S. Staton. Two cotensors in one: Presentations of algebraic theories for local state and fresh names. Electr. Notes Theor. Comput. Sci., 249: , [42] N. Swamy, N. Guts, D. Leijen, and M. Hicks. Lightweight monadic programming in ML. In ICFP. ACM, [43] W. Swierstra. Data types à la carte. J. Funct. Program., 18(4): , [44] S. Visscher. The effects package (0.2.2), [45] J. Voigtländer. Asymptotic improvement of computations over free monads. In MPC. Springer-Verlag, [46] P. Wadler. Monads for functional programming. In Advanced Functional Programming. Springer-Verlag, A. Performance Results All performance testing was conducted with the -O2 compiler flag enabled using a PC with a quad-core Intel i7-3770k CPU running at 3.50GHz CPU and 32GB of RAM, running GHC on Ubuntu Linux We used O Sullivan s criterion library [31] to sample each micro-benchmark ten times. The code for the micro-benchmarks can be found in the GitHub repository at: A.1 State As a basic sanity check we tested the following function on state: count :: SComp Int Int count = do i get; if i 0 then return i else do put (i 1); count We used 10 8 as the initial value for the state. We tested implementations using: the state monad, three different versions of standard deep handlers, and one implementation of shallow handlers. As a control, we also tested a pure version of count. In each case we used open handlers for interpreting state. pure state monad handlers (continuations) handlers (free monad) handlers (codensity) shallow handlers Table 1. State The results are shown in Table 1. GHC is optimised for monadic programming, so there is no cost to using a state monad over a pure program. The continuation monad implementation runs at two thirds of the speed of the baseline. The free monad implementation is a hundred times slower than the baseline. Using a codensity monad gives a two times speed-up to the free monad implementation. Shallow handlers are implemented using a free monad and are slowest of all. A.2 Flat Pipes We tested our pipes implementation using a flat pipeline previously used by the author of the pipes library for comparing performance between the pipes library and other libraries [13]. The pipeline consists of a producer that yields in turn the integers in the sequence [1.. n ], for some n, connected to a consumer that ignores all inputs and loops forever. The pipes library optionally takes advantage of GHC rewrite rules to define special code optimisations for pipes code. We tested against pipes with and without the rewrite rules enabled. The results are shown in Table 2 for n = The continuation monad implementation is nearly twice as fast as the pipes library without rewrite rules enabled. Enabling the rewrite rules makes a significant difference. In this case the pipes library is faster than the continuation monad implementation. The free monad and codensity implementations are slower than the pipes library, but the differential is much smaller than in the case of the count micro-benchmark. Interestingly, shallow handlers outperform the free monad implementation of standard handlers. pipes library pipes library + rewrites handlers (continuations) handlers (free monad) handlers (codensity) shallow handlers A.3 Nested Pipes Table 2. Flat Pipes To test the scalability of handlers we implemented a deeply-nested pipes computation constructed from 2 n sub-pipes, for a range of

14 values of n. The results are shown in Table 5. They are intriguing as the relative performance varies according to the number of sub-pipes. The relative performance is shown graphically in Figure 7. The pipes library always out-performs all of our libraries, even with GHC rewrite rules disabled. The continuation monad implementation is relatively constant at around two thirds the speed of the pipes library. What is particularly notable is that as the level of nesting increases, the performance of shallow handlers eventually overtakes that of the continuation monad implementation. One possible reason for the pipes library outperforming our continuation monad implementation on nested pipes is that it is in fact based on a free monad, and the implementation takes advantage of the reified representation of computations to optimise the case where an input is forwarded through several pipes. We are not sure why shallow pipes perform so well on deeplynested pipes, but suspect it may be due to the simpler definition of pipes for shallow handlers, as compared with that for standard handlers, opening up optimisation opportunities along the lines of those explicitly encoded in the pipes library. We conjecture that the anomalous dip at 2 11 sub-pipes for the bottom three lines in Figure 7 is due to cache effects. Relative performance ^9 2^10 2^11 2^12 2^13 Number of nested pipes pipes library pipes library+rewrites handlers (continuations) handlers (codensity) handlers (free) shallow handlers Figure 7. Relative Performance of Nested Pipes A.4 The n-queens Problem To test the performance of handlers that invoke the continuation zero or many times, we implemented the classic n-queens problem in terms of an n-ary Choose operation: [operation a.choose :: [a ] a ] We wrote a handler that returns the first correct solution for the n- queens problem, and tested against a hand-coded n-queens solver. We tested both algorithms with n = 20. hand-coded handlers Table 3. n-queens The results are shown in Table 3. The handler version is about two thirds the speed of the hand-coded version. A.5 Aspect-Oriented Programming Effect handlers can be used to implement a form of aspectoriented programming. We tested an expression evaluator taken from Oliveira et al. s work on monadic mixins [7]. The expression evaluator is extended to output logging information whenever entering or exiting a recursive call, and to output the environment whenever entering a recursive call. We compared a hand-coded evaluator with Oliveira et al. s mixin-based evaluator and an evaluator implemented using our continuation monad implementation of standard handlers. We tested each evaluator on the same randomly generated expression containing 2 12 leaf nodes. Implementation Time (ms) hand-coded 6516 mixins 6465 handlers (continuations) 6526 Table 4. Aspect-Oriented Programming The results are shown in Table 4. The performance is almost identical for each of the three implementations, indicating no abstraction overhead. 2 9 sub-pipes pipes library pipes library + rewrites handlers (continuations) handlers (free monad) handlers (codensity) shallow handlers sub-pipes pipes library pipes library + rewrites handlers (continuations) handlers (free monad) handlers (codensity) shallow handlers sub-pipes pipes library pipes library + rewrites handlers (continuations) handlers (free monad) handlers (codensity) shallow handlers sub-pipes pipes library pipes library + rewrites handlers (continuations) handlers (free monad) handlers (codensity) shallow handlers sub-pipes pipes library pipes library + rewrites handlers (continuations) handlers (free monad) handlers (codensity) shallow handlers Table 5. Nested Pipes

Moving from CS 61A Scheme to CS 61B Java Introduction Java is an object-oriented language. This document describes some of the differences between object-oriented programming in Scheme (which we hope you

Introducing Formal Methods Formal Methods for Software Specification and Analysis: An Overview 1 Software Engineering and Formal Methods Every Software engineering methodology is based on a recommended

The Clean programming language Group 25, Jingui Li, Daren Tuzi The Clean programming language Overview The Clean programming language first appeared in 1987 and is still being further developed. It was

Monads for functional programming Philip Wadler, University of Glasgow Department of Computing Science, University of Glasgow, G12 8QQ, Scotland (wadler@dcs.glasgow.ac.uk) Abstract. The use of monads to

Appendix E Glossary of Object Oriented Terms abstract class: A class primarily intended to define an instance, but can not be instantiated without additional methods. abstract data type: An abstraction

Overview Elements of Programming Languages Lecture 12: Object-oriented functional programming James Cheney University of Edinburgh November 6, 2015 We ve now covered: basics of functional and imperative

Types, Polymorphism, and Type Reconstruction Sources This material is based on the following sources: Pierce, B.C., Types and Programming Languages. MIT Press, 2002. Kanellakis, P.C., Mairson, H.G. and

Chapter 15 Functional Programming Languages Introduction - The design of the imperative languages is based directly on the von Neumann architecture Efficiency (at least at first) is the primary concern,

Embedded Software Development with MPS Markus Voelter independent/itemis The Limitations of C and Modeling Tools Embedded software is usually implemented in C. The language is relatively close to the hardware,

Data Abstraction and Hierarchy * This research was supported by the NEC Professorship of Software Science and Engineering. Barbara Liskov Affiliation: MIT Laboratory for Computer Science Cambridge, MA,

1 Introduction The purpose of this assignment is to write an interpreter for a small subset of the Lisp programming language. The interpreter should be able to perform simple arithmetic and comparisons

CMSC 858T: Randomized Algorithms Spring 2003 Handout 8: The Local Lemma Please Note: The references at the end are given for extra reading if you are interested in exploring these ideas further. You are

Curriculum Map Discipline: Computer Science Course: C++ August/September: How can computer programs make problem solving easier and more efficient? In what order does a computer execute the lines of code

A Propositional Dynamic Logic for CCS Programs Mario R. F. Benevides and L. Menasché Schechter {mario,luis}@cos.ufrj.br Abstract This work presents a Propositional Dynamic Logic in which the programs are

Interpreters and virtual machines Michel Schinz 2007 03 23 Interpreters Interpreters Why interpreters? An interpreter is a program that executes another program, represented as some kind of data-structure.

Fundamentals of Java Programming This document is exclusive property of Cisco Systems, Inc. Permission is granted to print and copy this document for non-commercial distribution and exclusive use by instructors

Theory of Computation Lecture Notes Abhijat Vichare August 2005 Contents 1 Introduction 2 What is Computation? 3 The λ Calculus 3.1 Conversions: 3.2 The calculus in use 3.3 Few Important Theorems 3.4 Worked

Programming Language Concepts for Software Developers Peter Sestoft IT University of Copenhagen, Denmark sestoft@itu.dk Abstract This note describes and motivates our current plans for an undergraduate

New Generation of Software Development Terry Hon University of British Columbia 201-2366 Main Mall Vancouver B.C. V6T 1Z4 tyehon@cs.ubc.ca ABSTRACT In this paper, I present a picture of what software development

From Faust to Web Audio: Compiling Faust to JavaScript using Emscripten Myles Borins Center For Computer Research in Music and Acoustics Stanford University Stanford, California United States, mborins@ccrma.stanford.edu

PROBLEM SOLVING WITH SEVENTH EDITION WALTER SAVITCH UNIVERSITY OF CALIFORNIA, SAN DIEGO CONTRIBUTOR KENRICK MOCK UNIVERSITY OF ALASKA, ANCHORAGE PEARSON Addison Wesley Boston San Francisco New York London

A single minimal complement for the c.e. degrees Andrew Lewis Leeds University, April 2002 Abstract We show that there exists a single minimal (Turing) degree b < 0 s.t. for all c.e. degrees 0 < a < 0,

The Import & Export of Data from a Database Introduction The aim of these notes is to investigate a conceptually simple model for importing and exporting data into and out of an object-relational database,

A Value Transmission Method for Abstract Data Types M. HERLIHY and B. LISKOV Massachusetts Institute of Technology Abstract data types have proved to be a useful technique for structuring systems. In large

Anatomy of Programming Languages William R. Cook Copyright (C) 2013 2 Chapter 1 Preliminaries Preface What? This document is a series of notes about programming languages, originally written for students

Answer first, then check at the end. Review questions for Chapter 9 True/False 1. A compiler translates a high-level language program into the corresponding program in machine code. 2. An interpreter is

2008 AGI-Information Management Consultants May be used for personal purporses only or by libraries associated to dandelon.com network. Computing Concepts with Java Essentials 3rd Edition Cay Horstmann

The Classes P and NP We now shift gears slightly and restrict our attention to the examination of two families of problems which are very important to computer scientists. These families constitute the

inary Trees 1 A binary tree is either empty, or it consists of a node called the root together with two binary trees called the left subtree and the right subtree of the root, which are disjoint from each

CHAPTER 7 GENERAL PROOF SYSTEMS 1 Introduction Proof systems are built to prove statements. They can be thought as an inference machine with special statements, called provable statements, or sometimes

Towards a Framework for Generating Tests to Satisfy Complex Code Coverage in Java Pathfinder Matt Department of Computer Science and Engineering University of Minnesota staats@cs.umn.edu Abstract We present

Java Application Developer Certificate Program Competencies After completing the following units, you will be able to: Basic Programming Logic Explain the steps involved in the program development cycle

Blame for All Amal Ahmed Indiana University amal@cs.indiana.edu Robert Bruce Findler Northwestern University robby@eecs.northwestern.edu Jeremy G. Siek University of Colorado at Boulder jeremy.siek@colorado.edu