- 05 3月, 2015 2 次提交
-
-
由 Huon Wilson 提交于
-
由 Huon Wilson 提交于
Unstable items used in a macro expansion will now always trigger stability warnings, *unless* the unstable items are directly inside a macro marked with `#[allow_internal_unstable]`. IOW, the compiler warns unless the span of the unstable item is a subspan of the definition of a macro marked with that attribute. E.g. #[allow_internal_unstable] macro_rules! foo { ($e: expr) => {{ $e; unstable(); // no warning only_called_by_foo!(); }} } macro_rules! only_called_by_foo { () => { unstable() } // warning } foo!(unstable()) // warning The unstable inside `foo` is fine, due to the attribute. But the `unstable` inside `only_called_by_foo` is not, since that macro doesn't have the attribute, and the `unstable` passed into `foo` is also not fine since it isn't contained in the macro itself (that is, even though it is only used directly in the macro). In the process this makes the stability tracking much more precise, e.g. previously `println!("{}", unstable())` got no warning, but now it does. As such, this is a bug fix that may cause [breaking-change]s. The attribute is definitely feature gated, since it explicitly allows side-stepping the feature gating system.
-
- 03 3月, 2015 3 次提交
-
-
由 Huon Wilson 提交于
The API this exposes is a little strange (being attached to `static`s), so it makes sense to conservatively feature gate it. If it is highly popular, it is possible to reverse this gating.
-
由 Manish Goregaokar 提交于
-
由 Florian Zeitz 提交于
This changes the type of some public constants/statics in libunicode. Notably some `&'static &'static [(char, char)]` have changed to `&'static [(char, char)]`. The regexp crate seems to be the sole user of these, yet this is technically a [breaking-change]
-
- 26 2月, 2015 1 次提交
-
-
由 Steven Fackler 提交于
-
- 25 2月, 2015 1 次提交
-
-
由 Felix S. Klock II 提交于
Fix #22173
-
- 24 2月, 2015 2 次提交
-
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
- 19 2月, 2015 2 次提交
-
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
they are used without a feature-gate. This is both kinder to existing code and should make it easier to land this PR, since we don't have to catch EVERY SINGLE SUFFIX.
-
- 17 2月, 2015 3 次提交
-
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
-
- 16 2月, 2015 5 次提交
-
-
由 Manish Goregaokar 提交于
- We shouldn't be using `check_name` here at all - `contains_name(ref_slice(foo), bar)` is redundant, `contains_name` just iterates over its first arg and calls `check_name` - match would be better than a bunch of ifs
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
-
由 Felix S. Klock II 提交于
The other cases: `concat_idents!`, `log_syntax!`, and `trace_macros!`, (these macros, with `asm!`, are handled (eagerly) in feature_gate.rs).
-
由 Felix S. Klock II 提交于
-
- 13 2月, 2015 2 次提交
-
-
由 Felix S. Klock II 提交于
Added a second note about keeping the reference.md list up-to-date to the bottom of the list, since not everyone (including me) reads the big comment at the top of it. :) Ensured that the feature gate list in reference.md is kept in alphabetical order.
-
由 Felix S. Klock II 提交于
Rollup merge (373cbab5) of PR #20723 accidentally reverted a portion of commit 8327bcc1 which shifted `slicing_syntax` from Active to Accepted.
-
- 11 2月, 2015 4 次提交
-
-
由 Felix S. Klock II 提交于
just say "experimental."
-
由 Felix S. Klock II 提交于
See RFC 320, "Non-zeroing dynamic drops." Fix #22173 [breaking-change]
-
由 Felix S. Klock II 提交于
-
由 Felix S. Klock II 提交于
Switch feature-gate checker from `box_syntax` to `box_patterns` when visiting a pattern. (Having to opt into both `box_syntax` and `box_patterns` seemed unnecessary.) [breaking-change]
-
- 10 2月, 2015 1 次提交
-
-
由 Keegan McAllister 提交于
#[plugin] #[no_link] extern crate bleh; becomes a crate attribute #![plugin(bleh)] The feature gate is still required. It's almost never correct to link a plugin into the resulting library / executable, because it will bring all of libsyntax and librustc with it. However if you really want this behavior, you can get it with a separate `extern crate` item in addition to the `plugin` attribute. Fixes #21043. Fixes #20769. [breaking-change]
-
- 08 2月, 2015 1 次提交
-
-
由 Keegan McAllister 提交于
Fixes #21833. [breaking-change]
-
- 06 2月, 2015 3 次提交
-
-
由 GuillaumeGomez 提交于
-
由 GuillaumeGomez 提交于
-
由 Jorge Aparicio 提交于
-
- 05 2月, 2015 2 次提交
-
-
由 Brian Anderson 提交于
The 'stable_features' lint helps people progress from unstable to stable Rust by telling them when they no longer need a `feature` attribute because upstream Rust has declared it stable. This compares to the existing 'unstable_features', which is used to implement feature staging, and triggers on *any* use of `#[feature]`.
-
由 Joseph Crail 提交于
The spelling corrections were made in both documentation comments and regular comments.
-
- 04 2月, 2015 1 次提交
-
-
由 Manish Goregaokar 提交于
-
- 03 2月, 2015 1 次提交
-
-
由 Jorge Aparicio 提交于
-
- 31 1月, 2015 1 次提交
-
-
由 Alex Crichton 提交于
Also some tidying up of a bunch of crate attributes
-
- 29 1月, 2015 1 次提交
-
-
由 Flavio Percoco 提交于
-
- 27 1月, 2015 1 次提交
-
-
由 Brian Anderson 提交于
-
- 23 1月, 2015 1 次提交
-
-
由 Brian Anderson 提交于
-
- 22 1月, 2015 2 次提交
-
-
由 Brian Anderson 提交于
Does a sanity check of the version numbers.
-
由 Brian Anderson 提交于
-