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…
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.
-
-
Well… I don’t think that should be the definition of stability (in any language), just the subset of it that can (theoretically) be checked. And sure, such a check wouldn’t completely rule out breakage. But I think it’d still be massively better than not having it.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.