OpenE2K
/
rust
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fix rustc-std-workspace-core documentation

This commit is contained in:
Daniel Le 2020-12-20 15:21:17 +08:00
parent 29e32120c3
commit e614a720b6
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
library/rustc-std-workspace-core/README.md
View File

@ -4,12 +4,12 @@ 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 reexports all of its contents. The crate is the crux of empowering the standard
library to depend on crates from crates.io library to depend on crates from crates.io
Crates on crates.io that the standard library depend on the Crates on crates.io that the standard library depend on need to depend on the
`rustc-std-workspace-core` crate from crates.io. On crates.io, however, this `rustc-std-workspace-core` crate from crates.io, which is empty. We use
crate is empty. We use `[patch]` to override it to this crate in this `[patch]` to override it to this crate in this repository. As a result, crates
repository. As a result, crates on crates.io will draw a dependency edge to on crates.io will draw a dependency edge to `libcore`, the version defined in
`libcore`, the version defined in this repository. That should draw all the this repository. That should draw all the dependency edges to ensure Cargo
dependency edges to ensure Cargo builds crates successfully! builds crates successfully!
Note that crates on crates.io need to depend on this crate with the name `core` 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: for everything to work correctly. To do that they can use: