News for hackers. Stuff that matters.
Re:The semver trick (2019) by tantalor on Thursday December 26, 2024 @03:24PM (#42517504)
Not knowing rust, this is pretty meaningless to me.

Is this trick relevant outside of rust?

Re:The semver trick (2019) by adastra22 on Thursday December 26, 2024 @03:55PM (#42517744)
Rust has a nice semver-based package management tool called cargo. One thing rust/cargo does really well is packaging up different versions of the same dependency for the same build. E.g. your project can update to widget=2.0 while some of your downstream dependencies are still stuck on the 1.x release branch. Cargo's semver support means that those dependencies can be automatically upgrade to support newer 1.x releases, but they will not work with 2.x without the package maintainer's intervention. In the mean time it just compiles and links to both, while keeping them isolated.

Usually this is great. You avoid dependency hell while only trading off some compiled binary size. Sometimes it fails when a package must have only one version, e.g. because you're passing around data types from that package to/from your dependencies which use the old version, but part of rust/cargo's trick is that types drawn from different versions of the same package are distinct types. So you get a compile-time type check error.

Solution: the widget package maintainer pushes out a final 1.x release which itself depends on widget=2, and is simply a shim that re-exports the API. This semver-violating trickery is basically a stealth upgrade that forces all upstream widget=1 pegged crates onto the new widget=2 release branch.

This trick is generic and relevant outside of rust, at least so far as other package managers user semver-aware dependency management.

Re:The semver trick (2019) by cmckn on Thursday December 26, 2024 @04:16PM (#42517883)
Why is any of that necessary?

If your imports look like:

    A -> B -> C

    A -> C
In the scenario you’re describing, can’t C just stay on older versions of B if the maintainers don’t want to upgrade A? Why would the maintainers of A try to force C to upgrade? Said another way, why would C upgrade A via this trick while pretending they didn’t upgrade?
Re:The semver trick (2019) by wakawaka28 on Thursday December 26, 2024 @05:30PM (#42518361)
I think I get how this works but other package managers would likely solve the problem by specifying that the v2 package "provides" the v1 interface, and then possibly deprecating or removing v1. At least I think that would work. It's not something I've sought to do. Most libraries in C or C++ do not support linkage of different versions in one app, so you must pick exactly one version to run with.
Re:The semver trick (2019) by Tuna-Fish on Thursday December 26, 2024 @05:38PM (#42518398)
The problem with this is that v2 by definition does not provide the v1 interface, or there would be no reason to bump up the major version number.

Using the trick, the last v1 package is a facade that constructs the old interface using the new package. To provide equivalent functionality, you basically have to do the same thing.

Re:The semver trick (2019) by wakawaka28 on Thursday December 26, 2024 @06:29PM (#42518696)
OK then if you want to keep the v1 interface exactly then you have to build a facade yourself. I don't think most libraries are capable of supporting that use case because of their semantic structure. Instead of employing a bunch of tricks to avoid fixing a couple of functions (the case where a facade makes sense), you should just fix the callers. That might not be easy for packages that are independently published (for example pypi or cargo packages) but it is possible in many package managers that have central teams of maintainers.
Re:The semver trick (2019) by adastra22 on Thursday December 26, 2024 @07:37PM (#42519019)
The whole thing is sus. If widget=2 can work as a drop-in replacement (non-breaking) for widget=1, then why the version bump in the first place?

But in the real world there are times when major versions are bumped without breaking changes. E.g. a bunch of crates maintained as part of a single project with a uniform versioning scheme.

Re:The semver trick (2019) by wakawaka28 on Friday December 27, 2024 @01:11AM (#42520269)
I think now there must be some kind of adapter code, even if auto-generated, that is a facade from v1 to v2. You can essentially use that to release a new v1 minor revision that depends on v2 for its implementation. But yeah the whole thing sounds sus, not easily applicable to other languages (where does this adapter code come from and how does it coexist with v2?), and like a bad practice even when it can work. You should really just migrate everyone to the new version instead of patching together something to handle stubborn users of the old version.
Re:The semver trick (2019) by edflsafoiewq on Thursday December 26, 2024 @04:14PM (#42517870)
It's relevant to any kind of dependency graph. Essentially it's converting

      A                  A       
     / \                / \      
   Cv2  B     into     |   B     
         \              \   \    
         Cv1             \  Cv1  
                          \ /    
                          Cv2    
Suppose some exported symbol, X, didn't change from Cv1 to Cv2. In the former, A gets two copies of X depending on which path it took up the dependency tree. In the latter, there's only one copy since both paths terminate in the same place.
Re:The semver trick (2019) by jerf on Thursday December 26, 2024 @03:47PM (#42517684)
I've used something very similar in Go. I can't point to it because it's an internal repository, but it allowed for relatively smooth co-existence between a v1 and a v2 of a particular package that had one aspect that was hard-to-upgrade, but also, generally rarely used compared to the rest. The rest of the types were fully identical because v1 simply re-exported the v2 types, so Go only complains if you try to cross the streams with the specifically-changed but rarely-used types, which is exactly the complaint I want.

In the case of Go I'm not sure if it's important that v1 specifically re-export the v2; I think it would work equally well either way. But it's at least very similar.

Re:The semver trick (2019) by clhodapp on Thursday December 26, 2024 @03:57PM (#42517753)
This feels like something similar would almost be relevant in Java Platform Modules, since modules also have the ability to re-export classes that they've imported. However, there are some small limitations that would make it annoying to adopt this pattern: Having more than one version of the same classname available in different modules requires boilerplate and it's difficult to define over some of the classes of a module that your module imports.
Re:The semver trick (2019) by Xylakant on Thursday December 26, 2024 @03:42PM (#42517646)
Theoretically, it can be. However, it’s only relevant in specific circumstances that Rust happens to provide, for example one of the requirements is that the package manager / build system allows you to have two different versions of the same dependencies in a single binary - which is comparatively rare.