[rust-dev] Deprecating rustpkg

Corey Richardson corey at octayn.net
Thu Jan 30 15:05:13 PST 2014


On Thu, Jan 30, 2014 at 6:02 PM, Tony Arcieri <bascule at gmail.com> wrote:
> On Thu, Jan 30, 2014 at 2:28 PM, Tim Chevalier <catamorphism at gmail.com>
> wrote:
>>
>> ...the design was to treat different versions of the same package as
>> separate entities that can coexist. That's why package IDs include optional
>> versions.
>
>
> RubyGems does this, and I think it was a mistake that has lead to an
> explosion of incidental complexity in the form of things like gemsets.
>
> In the presence of a dependency resolver this feature is not only useless
> but annoying.
>

I find it both useful and pleasant. I can write a lib that uses
version X of libA, but have an application using version Y of libA be
able to link to me. This isn't a problem in Rust because symbol names
include the version (as well as the hash).


More information about the Rust-dev mailing list