Go’s new “minimal version selection” system (https://research.swtch.com/vgo-mvs ) is interesting. It‘s tempting to just write off as NIH: “lockfiles are complicated, so let’s not use them and instead /never upgrade anything ever/ by default”. Simplicity at a cost, like other Go decisions…
Isn’t that literally reducible to the halting problem? (This isn’t a pedantic point; it seems intractable.)
-
-
Well, I’m actually just thinking of ensuring the types are compatible. Runtime behavior is not tractable, but especially in a language like Rust, “it compiles” is a strong guarantee. (…although technically Rust’s type system is TC, so it still reduces to the halting problem :)
-
I’m not sure that’s strong enough of a guarantee. Go used that criterion to define stability and broke code due to behavioral differences.
- 1 more reply
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.