diff options
| author | Alex Crichton <alex@alexcrichton.com> | 2017-02-15 07:57:59 -0800 |
|---|---|---|
| committer | Alex Crichton <alex@alexcrichton.com> | 2017-03-23 11:28:00 -0700 |
| commit | e341d603fe7c35ce174bd2e54e47ed6941ea4b03 (patch) | |
| tree | b3e32ba82ad906907e681dd4a3ca142c95cc3937 /src/libstd/net | |
| parent | 90346eae18e83887517e096c17678a74838ff995 (diff) | |
| download | rust-e341d603fe7c35ce174bd2e54e47ed6941ea4b03.tar.gz rust-e341d603fe7c35ce174bd2e54e47ed6941ea4b03.zip | |
Remove internal liblog
This commit deletes the internal liblog in favor of the implementation that
lives on crates.io. Similarly it's also setting a convention for adding crates
to the compiler. The main restriction right now is that we want compiler
implementation details to be unreachable from normal Rust code (e.g. requires a
feature), and by default everything in the sysroot is reachable via `extern
crate`.
The proposal here is to require that crates pulled in have these lines in their
`src/lib.rs`:
#![cfg_attr(rustbuild, feature(staged_api, rustc_private))]
#![cfg_attr(rustbuild, unstable(feature = "rustc_private", issue = "27812"))]
This'll mean that by default they're not using these attributes but when
compiled as part of the compiler they do a few things:
* Mark themselves as entirely unstable via the `staged_api` feature and the
`#![unstable]` attribute.
* Allow usage of other unstable crates via `feature(rustc_private)` which is
required if the crate relies on any other crates to compile (other than std).
Diffstat (limited to 'src/libstd/net')
0 files changed, 0 insertions, 0 deletions
