Though redo (which introduces no new languages, and uses a strict, small subset of make syntax) is an indication that excellent change-orientation can be more of a design pattern than a syntax pattern. It required some high-order (pun intended?) thinking to get there :)
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
Yup. In redo, that looks like: track all targets that have ever been built. If any of the inputs needed for that target ever change, build the outputs again.
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
This Tweet is unavailable.
-
To what end? Only for performance/incremental compilation – or something else entirely? (I have lately come to the conclusion that compilation speed only becomes an issue in language that are developed by adding features first – and asking how things will compile later.)
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
Executable code: from shit to "higher regard" and back to shit, in just three tweets.
3:10 AM - 8 Apr 2020
from Krakow, Poland
0 replies
0 retweets
2 likes
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.