Lazy evaluation is well-known from Haskell, but here is asynchronous lenient evaluation:pic.twitter.com/9dtjZY6ZSs
-
-
Replying to @TimSweeneyEpic
Why call it that instead of well-established dataflow programming (from the 60s)? https://en.wikipedia.org/wiki/Dataflow_programming …
1 reply 0 retweets 0 likes -
Replying to @niekstrom
Because it's now just an evaluation mode in a normal language, without special syntax or constructs.
1 reply 0 retweets 1 like -
Replying to @TimSweeneyEpic
Does "implicit future" better describe what you are thinking of? As in http://home.pipeline.com/~hbaker1/Futures.html …, https://en.wikipedia.org/wiki/Futures_and_promises#Implicit_vs._explicit …
1 reply 0 retweets 1 like -
Replying to @TimSweeneyEpic @niekstrom
All of my good ideas were invented by someone else in the 1980's. 
7:56 PM - 27 Jan 2017
0 replies
0 retweets
1 like
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.