3 ms·
That's essentially the solution Rust and Cargo adopt. It occasionally causes strange errors like "expected Foo, found Foo" (where the first Foo was, say, Foo ve
by pcwalton 11y ago
That's essentially the solution Rust and Cargo adopt. It occasionally causes strange errors like "expected Foo, found Foo" (where the first Foo was, say, Foo version 1.1 and the second was Foo version 1.2), but the compiler now detects this situation and tries to explain what's going on.
I'm certain I'm biased, but in my experience it's been the most robust way to handle versioning that I've dealt with.
- stcredzero 11y agoI proposed this in a Smalltalk newsgroup over a decade ago. The reaction? I was ridiculed. Imports naming specific versions would also allow better integration of code/build into a version control system. Actually, the entire OS should be built with version control in mind from the ground up.
- CyberDildonics 11y agoNo truly good idea will ever escape ridicule.
- bjz_ 11y ago> the compiler now detects this situation and tries to explain what's going on. Oh really? That's great news! I remember having that problem earlier this year and thinking that it wasn't the greatest from a usability standpoint.