Hacker News Reader

Can you elaborate on the Rust problem or give me a pointer to something describing it?

I always thought that Rust is perfectly happy to link in conflicting versions of a module into the same binary.

I believe the problem appears when module A returns a value of type B@0.1, and that gets passed on to module C which actually expected a value of type B@0.2. This is a fundamental problem with having multiple versions of the same library used in the same program. The problem is much worse with any kind of dynamic boxing support, since it visibility of the type can't be guaranteed statically.

Of course, for many programs, those values are not returned outside the original scope and all works well.

Cargo is closer to NPM. It does not require SAT resolution. You can have conflicting major versions of the same dependency.

This was my point as well? You can have different versions of the same library, as long as you do not try to pass around data from one version to the other - which would not work in any language anyway.

Only if there is no interaction between them in your code

Reply on news.ycombinator.com