about summary refs log tree commit diff
path: root/src/libstd/ascii.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2017-03-26 04:26:22 +0000
committerbors <bors@rust-lang.org>2017-03-26 04:26:22 +0000
commit7dd4e2db785c8ec360a989f69891b1e97dd4d369 (patch)
tree223f7115ef30e9ec99983d7fad3bcf7ded5b9596 /src/libstd/ascii.rs
parent0f5ddb953aafa8c63098dc1a32d3fdebaad82a5b (diff)
parente341d603fe7c35ce174bd2e54e47ed6941ea4b03 (diff)
downloadrust-7dd4e2db785c8ec360a989f69891b1e97dd4d369.tar.gz
rust-7dd4e2db785c8ec360a989f69891b1e97dd4d369.zip
Auto merge of #40347 - alexcrichton:rm-liblog, r=brson
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/ascii.rs')
0 files changed, 0 insertions, 0 deletions