rust/src/librustc_back
Alex Crichton e341d603fe 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).
2017-03-23 11:28:00 -07:00
..
target Update usages of 'OSX' (and other old names) to 'macOS'. 2017-03-12 14:59:04 -04:00
Cargo.toml Remove internal liblog 2017-03-23 11:28:00 -07:00
dynamic_lib.rs std: Stabilize APIs for the 1.10 release 2016-05-24 09:00:39 -07:00
lib.rs Remove not(stage0) from deny(warnings) 2016-12-29 21:07:20 -08:00
slice.rs std: Stabilize library APIs for 1.5 2015-10-25 09:36:32 -07:00
tempdir.rs try! -> ? 2016-03-22 22:01:37 -05:00