Re:Go and Versioning: Minimal Version Selection
by dilap on Thursday February 22, 2018 @12:52AM
(#16435421)
No good reason, really :-) -- just a gut feeling/bias that when problems move from "tricky" to "easy", people end up creating new/unexpected tooling as a result, just because it's easier.
Might well be totally irrelevant here.
Sadly I don't know Rust (yet!), but Cargo certainly seems widely loved and admired.
Perusing the resolver code was pleasant, and impressive. We've come a long way from when you'd pull back the covers on a C++ std library or (god help you) boost, and run away screaming in terror.
The future is bright!
Besides, I suspect that if you restrict your Cargo graphs to use only the features that this Go proposal supports (minimal version pinning, in particular), then the algorithm is no longer NP-hard. There's no "Go magic" here: it's that just Go chooses not to implement features that could theoretically be slow (but aren't slow in practice).