cargo should install to ./.cargo by default instead of ~/.cargo

[brson]

This is what npm does and it's pretty cool that it keeps all your projects isolated.

[nikomatsakis]

+1

[killerswan]

So when you want to install something onto your system path (if ~/.cargo/bin is on the path), just cd ~ and install, but whenever you just want a local project copy, cd project_XYZ and install?

[brson]

Not sure. It looks like npm has two modes, local, and global. local puts it into the current working directory, and global puts it at the install prefix. It doesn't even have a mode to put it under the user's directory.

[killerswan]

For Haskell, Cabal-Dev does sandboxed installs like that as a way to compensate for the hellish way that Cabal fails to support multiple versions of libraries and has no uninstall option. It is easy to use, but not simple (to borrow Rich Hickey's terminology).

Can some of this dependency sandboxing be automated through import statements, rather than left as something every library user has to manually do?

[graydon]

We have versioning. It's not complete, but it's an Actual Concept in rust linkage rules.

[graydon]

I believe #1760 fixed this.