Explicit standard library dependencies

[Ericson2314]

(Split from of rust-lang/rfcs#1133)

The first task is to agree on a syntax for explicit stdlib deps. That RFC proposed

[depedencies]
std = { version = "*", stdlib = true }

But, if we are confident we can reserve the name on crates.io of everything that's part of the standard library (or isn't part of the standard library but exists in the sysroot), we don't even need a new syntax!

[depedencies]
std = "*" # work's just fine!

The second task is to decide whether version bounds are permitted in full generality, or restricted. Plausible restrictions would be:

• Exactly match the overall crate language version restrictions (however that pans out)
• Must be unrestricted (*), with the intent that the language version restriction will effectively restrict it anyways.

CC @japaric @nrc

[stale]

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you for contributing!

(The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.)

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

[Ericson2314]

Last I heard this sort of work might get priorized after the 2018 edition crunch time, so I'm just waiting for that.

[CodeSandwich]

@Ericson2314 2018 edition is out 🎉 Any news regarding this project?

[Ericson2314]

@CodeSandwich I don't have time to just make a PR and see if it's accepted (I've already tried that). If anyone wants to officially road-map this and #5003 (a good first goal is leveraging them in the Rust build system), they should comment in these threads and then I'll response.

[deliciouslytyped]

Is there any progress on this?
I'd like to vendor stuff for xargo to be able to do an offline build (actually I'm not sure saying that even makes sense since that code is in the rust-src component?)

[Ericson2314]

https://github.com/rust-lang/wg-cargo-std-aware is supposed to cover these sorts of things, I am not sure they've gotten to surface syntax in Cargo files yet.