| var $jscomp = $jscomp || {}; | |
| $jscomp.scope = {}; | |
| $jscomp.arrayIteratorImpl = function (h) { | |
| var n = 0; | |
| return function () { | |
| return n < h.length ? { done: false, value: h[n++] } : { done: true }; | |
| }; | |
| }; | |
| $jscomp.arrayIterator = function (h) { | |
| return { next: $jscomp.arrayIteratorImpl(h) }; |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <title>THREE.JS WORLD</title> | |
| <script type="text/javascript" src="https://cdnjs.cloudflare.com/ajax/libs/three.js/r73/three.js"></script> | |
| <style> | |
| body { | |
| /* set margin to 0 and overflow to hidden, to | |
| use the complete page */ |
| {-# Language TypeSynonymInstances, FlexibleInstances #-} | |
| module Algj where | |
| import Debug.Trace | |
| import Data.Maybe | |
| import qualified Data.Map as M | |
| import qualified Data.Set as S | |
| import Control.Monad.Trans.State |
| {-# Language TypeSynonymInstances, FlexibleInstances #-} | |
| module Algw where | |
| import Data.Maybe | |
| import qualified Data.Map as M | |
| import qualified Data.Set as S | |
| import Control.Monad.Trans.State |
This is the final part of a series about Algebraic Effects and Handlers.
So we've come to the core topic. The reality is that we've already covered most of it in the previous parts. Especially, in the third part, where we saw delimited continuations at work.
This is the third part of a series about Algebraic Effects and Handlers.
In the preceding parts, we introduced the notions of continuations and control transfer. We saw how to capture the current
This is the second part of a series about Algebraic Effects and Handlers.
Note: initially I planned a 3-part series, but since the current post on undelimited continuations ended up taking
| function isGenerator(x) { | |
| return x != null && typeof x.next === "function" | |
| } | |
| function isFrame(x) { | |
| return x != null && x._type_ === 'call_frame' | |
| } | |
| function call(genFunc, ...args) { |
This is the first post of a series about Algebraic Effects and Handlers.
There are 2 ways to approach this topic:
Both approaches are valuables and give different insights on the topic. However, not everyone (including me), has the prerequisites to grasp the concepts of Category theory and Abstract Algebra. On the other hand, the operational approach is accessible to a much wider audience of programmers even if it doesn't provide the full picture.
| // We model the call stack using a linked list of Generators | |
| // Each Generator has a _return field pointing back to its parent | |
| function stepGen(gen, arg) { | |
| const {done, value} = gen.next(arg) | |
| if(done) { | |
| if(gen._return) { | |
| stepGen(gen._return, value) | |
| } |