Collapsing Towers of Interpreters: This is the holy grail of compiler optimization tech, which no compiler or interpreter quite manages to achieve. http://lampwww.epfl.ch/~amin/pub/collapsing-towers.pdf …
-
-
Replying to @Thealternator4
The coroutine issue is complicated. I believe we need an asynchronous execution model that uses effects typing to ensure effects are issued in an observably correct order. I think it’s best to build that on futures rather than coroutines.
1 reply 0 retweets 2 likes -
Replying to @TimSweeneyEpic
However, we also need an approach for iterating over collections of values produced by arbitrary sources where production and consumption are separated modularity. I believe first-class failure and backtracking rather than coroutines are the right answer.
1 reply 0 retweets 2 likes -
Replying to @TimSweeneyEpic
In all of these cases, the high level features I proposed could be implemented internally using coroutines as a low-level building block. They more cleanly separate present from past than functional continuation-passing-style.
1 reply 0 retweets 2 likes
Much of what I’m saying here may be inscrutable till I publish a clearer outline of how such a runtime would work.
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.