rust/src/tools/rustc-std-workspace-core
David Tolnay 08cd34e4fc
Switch to SPDX 2.1 license expression
According to the Cargo Reference:
https://doc.rust-lang.org/cargo/reference/manifest.html

> This is an SPDX 2.1 license expression for this package. Currently
> crates.io will validate the license provided against a whitelist of
> known license and exception identifiers from the SPDX license list
> 2.4. Parentheses are not currently supported.
>
> Multiple licenses can be separated with a `/`, although that usage
> is deprecated. Instead, use a license expression with AND and OR
> operators to get more explicit semantics.
2019-05-09 15:40:01 -07:00
..
Cargo.toml Switch to SPDX 2.1 license expression 2019-05-09 15:40:01 -07:00
lib.rs rustc-std-workspace-core => 2018 2019-02-08 15:05:04 +09:00
README.md std: Depend directly on crates.io crates 2018-12-11 21:08:22 -08:00

The rustc-std-workspace-core crate

This crate is a shim and empty crate which simply depends on libcore and reexports all of its contents. The crate is the crux of empowering the standard library to depend on crates from crates.io

Crates on crates.io that the standard library depend on the rustc-std-workspace-core crate from crates.io. On crates.io, however, this crate is empty. We use [patch] to override it to this crate in this repository. As a result, crates on crates.io will draw a dependency edge to libcore, the version defined in this repository. That should draw all the dependency edges to ensure Cargo builds crates successfully!

Note that crates on crates.io need to depend on this crate with the name core for everything to work correctly. To do that they can use:

core = { version = "1.0.0", optional = true, package = 'rustc-std-workspace-core' }

Through the use of the package key the crate is renamed to core, meaning it'll look like

--extern core=.../librustc_std_workspace_core-XXXXXXX.rlib

when Cargo invokes the compiler, satisfying the implicit extern crate core directive injected by the compiler.