to be honest, i don't want those stages to communicate bidirectionally.
The runtime may find opportunities to multithread stuff, but there should be no observable consequences to it in a user program.
-
-
i see. hm. so when you say you want futures, are you saying you want haskell-style lazy evaluation? i considered it,
-
It's not exactly lazy, it's eager evaluation that starts sequentially but may go asynchronously out-of-order due to dependencies.
- 8 more replies
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.