3 ms·
What a waste that they did the work with an obligate-GC language and runtime. Without, it would be directly useful in making a verified OS and verified embedded
by ncmncm 8y ago
What a waste that they did the work with an obligate-GC language and runtime. Without, it would be directly useful in making a verified OS and verified embedded systems.
But Academia demands GC in any linguistic system, and systematically ignores all results that avoid it.
- xrchz 8y agohttps://github.com/CakeML/cakeml/issues/111 https://github.com/CakeML/cakeml/issues/111
- whitten 8y agoI read through the issue #111 you referenced. Both comments are from 2016, rather than any from this year. Perhaps you could reply and tell us the significance you see in this issue, and why it hasn't been addressed in at least two years.
- AgentOrange1234 8y agoWhile verified os/embedded systems would be great, is there not also value in trustworthy compilation of applications? A great deal of real software is written in java, python, js, swift, etc. ML may not be your cup of tea, but it’s a really nice language, and dismissing this as wasted work seems really harsh.
- ncmncm 8y agoHow much good do you get from proving an application program correct when it runs on an unreliable OS? I quite like the MLs, but would like to see a non-GC one.
- earthicus 8y agoThe mlkit compiler [1] for Standard ML pioneered region based manual memory management, and was a primary design inspiration for Rust's memory system [2]. This research project (CakeML) has a different, and perfectly valid set of goals. [1] http://elsman.com/mlkit/ http://elsman.com/mlkit/ [2] https://doc.rust-lang.org/reference/influences.html https://doc.rust-lang.org/reference/influences.html