<p dir="auto">I believe that it's a better choice to have the std library on crates.io, instead of in /usr/local. It makes it easier to have alternative standard libraries, and the compilers shouldn't really link with it automatically anyway. It also makes it easier to build for new targets, making cross compilation multiple grades of magnitude easier.</p>
<p dir="auto">The standard library requires on a rust version, but implementing a rustc version requirement shouldn't be too hard.</p>
<p dir="auto">The only argument I've so far heard against this, is that it'd require people to update their Cargo.lock if they are using cargo, or manually update the std if they are not. While this is true, most people <em>will</em> be using cargo or a dependency manager, and updating the lock file shouldn't be an issue.</p>
<p dir="auto">Today I heard rust prefers explicit over implicit. Not implicitly linking against all the standard libraries would follow this.</p>
<p dir="auto">This is somewhat related to issue <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="49827422" data-permission-text="Title is private" data-url="https://github.com/rust-lang/rust/issues/19240" data-hovercard-type="issue" data-hovercard-url="/rust-lang/rust/issues/19240/hovercard" href="https://github.com/rust-lang/rust/issues/19240">#19240</a>.</p>
<p dir="auto">By putting the standard libraries all in one seperate repository, or even each one in their own, it'd make porting rust conciderably easier. It would remove the need to work inside the rustc file tree, and it would make the build process way easier.</p>