Separation is a nice principle, but if you want modules to be first class values and also contain importable operator parsers...
In my formulation, they are referentially transparent and invisible to code. You can't ask "is future A ready?"
-
-
Rather, you write "X=A+1" and get a new future that's ready when A is ready. Sort of a dual to Haskell thunks and lazy evaluation.
-
Despite all of this, side-effectful operations always execute in order relative to each other.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.