2012-12-03 18:48:01 -06:00
|
|
|
// Copyright 2012 The Rust Project Developers. See the COPYRIGHT
|
|
|
|
// file at the top-level directory of this distribution and at
|
|
|
|
// http://rust-lang.org/COPYRIGHT.
|
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
|
|
|
|
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
|
|
|
|
// option. This file may not be copied, modified, or distributed
|
|
|
|
// except according to those terms.
|
|
|
|
|
2014-09-10 17:35:21 -05:00
|
|
|
use ast;
|
|
|
|
use attr;
|
|
|
|
use codemap::DUMMY_SP;
|
|
|
|
use codemap;
|
|
|
|
use fold::Folder;
|
|
|
|
use fold;
|
|
|
|
use parse::token::InternedString;
|
|
|
|
use parse::token::special_idents;
|
|
|
|
use parse::token;
|
|
|
|
use ptr::P;
|
|
|
|
use util::small_vector::SmallVector;
|
2012-01-26 17:20:29 -06:00
|
|
|
|
2014-11-14 15:55:57 -06:00
|
|
|
pub fn maybe_inject_crates_ref(krate: ast::Crate, alt_std_name: Option<String>)
|
2013-09-27 21:46:09 -05:00
|
|
|
-> ast::Crate {
|
2014-02-05 15:15:24 -06:00
|
|
|
if use_std(&krate) {
|
2014-11-14 15:55:57 -06:00
|
|
|
inject_crates_ref(krate, alt_std_name)
|
2014-01-24 01:40:54 -06:00
|
|
|
} else {
|
2014-02-05 15:15:24 -06:00
|
|
|
krate
|
2014-01-24 01:40:54 -06:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-09-10 17:35:21 -05:00
|
|
|
pub fn maybe_inject_prelude(krate: ast::Crate) -> ast::Crate {
|
2014-02-05 15:15:24 -06:00
|
|
|
if use_std(&krate) {
|
2014-09-10 17:35:21 -05:00
|
|
|
inject_prelude(krate)
|
2012-01-26 17:20:29 -06:00
|
|
|
} else {
|
2014-02-05 15:15:24 -06:00
|
|
|
krate
|
2012-01-26 17:20:29 -06:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-09-07 16:57:26 -05:00
|
|
|
pub fn use_std(krate: &ast::Crate) -> bool {
|
2015-01-07 10:58:31 -06:00
|
|
|
!attr::contains_name(&krate.attrs[], "no_std")
|
2012-01-26 18:23:34 -06:00
|
|
|
}
|
2013-07-19 00:38:55 -05:00
|
|
|
|
2013-07-19 06:51:37 -05:00
|
|
|
fn no_prelude(attrs: &[ast::Attribute]) -> bool {
|
|
|
|
attr::contains_name(attrs, "no_implicit_prelude")
|
2013-07-16 23:23:17 -05:00
|
|
|
}
|
2012-01-26 18:23:34 -06:00
|
|
|
|
2014-03-05 08:36:01 -06:00
|
|
|
struct StandardLibraryInjector<'a> {
|
Preliminary feature staging
This partially implements the feature staging described in the
[release channel RFC][rc]. It does not yet fully conform to the RFC as
written, but does accomplish its goals sufficiently for the 1.0 alpha
release.
It has three primary user-visible effects:
* On the nightly channel, use of unstable APIs generates a warning.
* On the beta channel, use of unstable APIs generates a warning.
* On the beta channel, use of feature gates generates a warning.
Code that does not trigger these warnings is considered 'stable',
modulo pre-1.0 bugs.
Disabling the warnings for unstable APIs continues to be done in the
existing (i.e. old) style, via `#[allow(...)]`, not that specified in
the RFC. I deem this marginally acceptable since any code that must do
this is not using the stable dialect of Rust.
Use of feature gates is itself gated with the new 'unstable_features'
lint, on nightly set to 'allow', and on beta 'warn'.
The attribute scheme used here corresponds to an older version of the
RFC, with the `#[staged_api]` crate attribute toggling the staging
behavior of the stability attributes, but the user impact is only
in-tree so I'm not concerned about having to make design changes later
(and I may ultimately prefer the scheme here after all, with the
`#[staged_api]` crate attribute).
Since the Rust codebase itself makes use of unstable features the
compiler and build system to a midly elaborate dance to allow it to
bootstrap while disobeying these lints (which would otherwise be
errors because Rust builds with `-D warnings`).
This patch includes one significant hack that causes a
regression. Because the `format_args!` macro emits calls to unstable
APIs it would trigger the lint. I added a hack to the lint to make it
not trigger, but this in turn causes arguments to `println!` not to be
checked for feature gates. I don't presently understand macro
expansion well enough to fix. This is bug #20661.
Closes #16678
[rc]: https://github.com/rust-lang/rfcs/blob/master/text/0507-release-channels.md
2015-01-06 08:26:08 -06:00
|
|
|
alt_std_name: Option<String>
|
2013-08-29 14:10:02 -05:00
|
|
|
}
|
2012-12-23 16:41:37 -06:00
|
|
|
|
2014-03-05 08:36:01 -06:00
|
|
|
impl<'a> fold::Folder for StandardLibraryInjector<'a> {
|
2014-05-20 23:25:42 -05:00
|
|
|
fn fold_crate(&mut self, mut krate: ast::Crate) -> ast::Crate {
|
2014-07-20 00:40:39 -05:00
|
|
|
|
2014-09-01 10:59:23 -05:00
|
|
|
// The name to use in `extern crate "name" as std;`
|
2014-09-10 17:35:21 -05:00
|
|
|
let actual_crate_name = match self.alt_std_name {
|
2015-01-07 10:58:31 -06:00
|
|
|
Some(ref s) => token::intern_and_get_ident(&s[]),
|
2014-07-20 00:40:39 -05:00
|
|
|
None => token::intern_and_get_ident("std"),
|
|
|
|
};
|
|
|
|
|
2015-01-13 09:30:17 -06:00
|
|
|
krate.module.items.insert(0, P(ast::Item {
|
|
|
|
id: ast::DUMMY_NODE_ID,
|
|
|
|
ident: token::str_to_ident("std"),
|
2014-02-28 17:25:15 -06:00
|
|
|
attrs: vec!(
|
2014-12-31 22:43:46 -06:00
|
|
|
attr::mk_attr_outer(attr::mk_attr_id(), attr::mk_word_item(
|
|
|
|
InternedString::new("macro_use")))),
|
2015-01-13 09:30:17 -06:00
|
|
|
node: ast::ItemExternCrate(Some((actual_crate_name, ast::CookedStr))),
|
2014-01-16 15:27:27 -06:00
|
|
|
vis: ast::Inherited,
|
2014-01-01 00:53:22 -06:00
|
|
|
span: DUMMY_SP
|
2015-01-13 09:30:17 -06:00
|
|
|
}));
|
2014-05-20 23:25:42 -05:00
|
|
|
|
|
|
|
krate
|
2013-08-29 14:10:02 -05:00
|
|
|
}
|
2014-01-24 01:40:54 -06:00
|
|
|
}
|
|
|
|
|
2014-11-14 15:55:57 -06:00
|
|
|
fn inject_crates_ref(krate: ast::Crate, alt_std_name: Option<String>) -> ast::Crate {
|
2014-01-24 01:40:54 -06:00
|
|
|
let mut fold = StandardLibraryInjector {
|
Preliminary feature staging
This partially implements the feature staging described in the
[release channel RFC][rc]. It does not yet fully conform to the RFC as
written, but does accomplish its goals sufficiently for the 1.0 alpha
release.
It has three primary user-visible effects:
* On the nightly channel, use of unstable APIs generates a warning.
* On the beta channel, use of unstable APIs generates a warning.
* On the beta channel, use of feature gates generates a warning.
Code that does not trigger these warnings is considered 'stable',
modulo pre-1.0 bugs.
Disabling the warnings for unstable APIs continues to be done in the
existing (i.e. old) style, via `#[allow(...)]`, not that specified in
the RFC. I deem this marginally acceptable since any code that must do
this is not using the stable dialect of Rust.
Use of feature gates is itself gated with the new 'unstable_features'
lint, on nightly set to 'allow', and on beta 'warn'.
The attribute scheme used here corresponds to an older version of the
RFC, with the `#[staged_api]` crate attribute toggling the staging
behavior of the stability attributes, but the user impact is only
in-tree so I'm not concerned about having to make design changes later
(and I may ultimately prefer the scheme here after all, with the
`#[staged_api]` crate attribute).
Since the Rust codebase itself makes use of unstable features the
compiler and build system to a midly elaborate dance to allow it to
bootstrap while disobeying these lints (which would otherwise be
errors because Rust builds with `-D warnings`).
This patch includes one significant hack that causes a
regression. Because the `format_args!` macro emits calls to unstable
APIs it would trigger the lint. I added a hack to the lint to make it
not trigger, but this in turn causes arguments to `println!` not to be
checked for feature gates. I don't presently understand macro
expansion well enough to fix. This is bug #20661.
Closes #16678
[rc]: https://github.com/rust-lang/rfcs/blob/master/text/0507-release-channels.md
2015-01-06 08:26:08 -06:00
|
|
|
alt_std_name: alt_std_name
|
2014-01-24 01:40:54 -06:00
|
|
|
};
|
2014-02-05 15:15:24 -06:00
|
|
|
fold.fold_crate(krate)
|
2014-01-24 01:40:54 -06:00
|
|
|
}
|
|
|
|
|
2014-06-06 08:51:42 -05:00
|
|
|
struct PreludeInjector<'a>;
|
2014-01-24 01:40:54 -06:00
|
|
|
|
2014-03-05 08:36:01 -06:00
|
|
|
impl<'a> fold::Folder for PreludeInjector<'a> {
|
2014-05-20 23:25:42 -05:00
|
|
|
fn fold_crate(&mut self, mut krate: ast::Crate) -> ast::Crate {
|
Preliminary feature staging
This partially implements the feature staging described in the
[release channel RFC][rc]. It does not yet fully conform to the RFC as
written, but does accomplish its goals sufficiently for the 1.0 alpha
release.
It has three primary user-visible effects:
* On the nightly channel, use of unstable APIs generates a warning.
* On the beta channel, use of unstable APIs generates a warning.
* On the beta channel, use of feature gates generates a warning.
Code that does not trigger these warnings is considered 'stable',
modulo pre-1.0 bugs.
Disabling the warnings for unstable APIs continues to be done in the
existing (i.e. old) style, via `#[allow(...)]`, not that specified in
the RFC. I deem this marginally acceptable since any code that must do
this is not using the stable dialect of Rust.
Use of feature gates is itself gated with the new 'unstable_features'
lint, on nightly set to 'allow', and on beta 'warn'.
The attribute scheme used here corresponds to an older version of the
RFC, with the `#[staged_api]` crate attribute toggling the staging
behavior of the stability attributes, but the user impact is only
in-tree so I'm not concerned about having to make design changes later
(and I may ultimately prefer the scheme here after all, with the
`#[staged_api]` crate attribute).
Since the Rust codebase itself makes use of unstable features the
compiler and build system to a midly elaborate dance to allow it to
bootstrap while disobeying these lints (which would otherwise be
errors because Rust builds with `-D warnings`).
This patch includes one significant hack that causes a
regression. Because the `format_args!` macro emits calls to unstable
APIs it would trigger the lint. I added a hack to the lint to make it
not trigger, but this in turn causes arguments to `println!` not to be
checked for feature gates. I don't presently understand macro
expansion well enough to fix. This is bug #20661.
Closes #16678
[rc]: https://github.com/rust-lang/rfcs/blob/master/text/0507-release-channels.md
2015-01-06 08:26:08 -06:00
|
|
|
// only add `use std::prelude::*;` if there wasn't a
|
|
|
|
// `#![no_implicit_prelude]` at the crate level.
|
|
|
|
// fold_mod() will insert glob path.
|
2015-01-07 10:58:31 -06:00
|
|
|
if !no_prelude(&krate.attrs[]) {
|
2014-09-07 12:09:06 -05:00
|
|
|
krate.module = self.fold_mod(krate.module);
|
2014-01-24 01:40:54 -06:00
|
|
|
}
|
2014-05-20 23:25:42 -05:00
|
|
|
krate
|
2014-01-24 01:40:54 -06:00
|
|
|
}
|
2013-08-29 14:10:02 -05:00
|
|
|
|
2014-09-07 12:09:06 -05:00
|
|
|
fn fold_item(&mut self, item: P<ast::Item>) -> SmallVector<P<ast::Item>> {
|
2015-01-07 10:58:31 -06:00
|
|
|
if !no_prelude(&item.attrs[]) {
|
2014-04-14 10:30:31 -05:00
|
|
|
// only recur if there wasn't `#![no_implicit_prelude]`
|
2013-08-29 14:10:02 -05:00
|
|
|
// on this item, i.e. this means that the prelude is not
|
|
|
|
// implicitly imported though the whole subtree
|
2014-09-07 12:09:06 -05:00
|
|
|
fold::noop_fold_item(item, self)
|
2013-08-29 14:10:02 -05:00
|
|
|
} else {
|
2013-11-25 01:08:53 -06:00
|
|
|
SmallVector::one(item)
|
2013-08-29 14:10:02 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2015-01-13 09:30:17 -06:00
|
|
|
fn fold_mod(&mut self, mut mod_: ast::Mod) -> ast::Mod {
|
2013-08-29 14:10:02 -05:00
|
|
|
let prelude_path = ast::Path {
|
2014-01-01 00:53:22 -06:00
|
|
|
span: DUMMY_SP,
|
2013-08-29 14:10:02 -05:00
|
|
|
global: false,
|
2014-12-22 11:04:23 -06:00
|
|
|
segments: vec![
|
2013-08-29 14:10:02 -05:00
|
|
|
ast::PathSegment {
|
2014-02-13 23:07:09 -06:00
|
|
|
identifier: token::str_to_ident("std"),
|
2014-11-03 20:52:52 -06:00
|
|
|
parameters: ast::PathParameters::none(),
|
2013-08-29 14:10:02 -05:00
|
|
|
},
|
|
|
|
ast::PathSegment {
|
2014-02-13 23:07:09 -06:00
|
|
|
identifier: token::str_to_ident("prelude"),
|
2014-11-03 20:52:52 -06:00
|
|
|
parameters: ast::PathParameters::none(),
|
2014-12-22 11:04:23 -06:00
|
|
|
},
|
|
|
|
ast::PathSegment {
|
|
|
|
identifier: token::str_to_ident("v1"),
|
|
|
|
parameters: ast::PathParameters::none(),
|
|
|
|
},
|
|
|
|
],
|
2013-08-29 14:10:02 -05:00
|
|
|
};
|
|
|
|
|
2015-01-13 09:30:17 -06:00
|
|
|
let vp = P(codemap::dummy_spanned(ast::ViewPathGlob(prelude_path)));
|
|
|
|
mod_.items.insert(0, P(ast::Item {
|
|
|
|
id: ast::DUMMY_NODE_ID,
|
|
|
|
ident: special_idents::invalid,
|
|
|
|
node: ast::ItemUse(vp),
|
2014-09-07 12:09:06 -05:00
|
|
|
attrs: vec![ast::Attribute {
|
2014-08-12 22:31:30 -05:00
|
|
|
span: DUMMY_SP,
|
|
|
|
node: ast::Attribute_ {
|
|
|
|
id: attr::mk_attr_id(),
|
|
|
|
style: ast::AttrOuter,
|
2014-09-07 12:09:06 -05:00
|
|
|
value: P(ast::MetaItem {
|
2014-08-12 22:31:30 -05:00
|
|
|
span: DUMMY_SP,
|
|
|
|
node: ast::MetaWord(token::get_name(
|
|
|
|
special_idents::prelude_import.name)),
|
2014-09-07 12:09:06 -05:00
|
|
|
}),
|
2014-08-12 22:31:30 -05:00
|
|
|
is_sugared_doc: false,
|
|
|
|
},
|
2014-09-07 12:09:06 -05:00
|
|
|
}],
|
2014-01-16 15:27:27 -06:00
|
|
|
vis: ast::Inherited,
|
2014-01-01 00:53:22 -06:00
|
|
|
span: DUMMY_SP,
|
2015-01-13 09:30:17 -06:00
|
|
|
}));
|
|
|
|
|
|
|
|
fold::noop_fold_mod(mod_, self)
|
2013-08-29 14:10:02 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-09-10 17:35:21 -05:00
|
|
|
fn inject_prelude(krate: ast::Crate) -> ast::Crate {
|
2014-06-06 08:51:42 -05:00
|
|
|
let mut fold = PreludeInjector;
|
2014-02-05 15:15:24 -06:00
|
|
|
fold.fold_crate(krate)
|
2012-01-26 17:20:29 -06:00
|
|
|
}
|