- 16 2月, 2015 2 次提交
-
-
由 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 提交于
-
- 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 提交于
-
- 21 1月, 2015 2 次提交
-
-
由 Eduard Burtescu 提交于
-
由 Eduard Burtescu 提交于
-
- 17 1月, 2015 2 次提交
-
-
由 Huon Wilson 提交于
I don't know if this handling of SIMD types is correct for the C ABI on all platforms, so lets add an even finer feature gate than just the `simd` one. The `simd` one can be used with (relatively) little risk of complete nonsense, the reason for it is that it is likely that things will change. Using the types in FFI with an incorrect ABI will at best give absolute nonsense results, but possibly cause serious breakage too, so this is a step up in badness, hence a new feature gate.
-
由 Alex Crichton 提交于
These two attributes are used to change the entry point into a Rust program, but for now they're being put behind feature gates until we have a chance to think about them a little more. The #[start] attribute specifically may have its signature changed. This is a breaking change to due the usage of these attributes generating errors by default now. If your crate is using these attributes, add this to your crate root: #![feature(start)] // if you're using the #[start] attribute #![feature(main)] // if you're using the #[main] attribute cc #20064
-
- 12 1月, 2015 1 次提交
-
-
由 Manish Goregaokar 提交于
-
- 09 1月, 2015 2 次提交
-
-
由 Huon Wilson 提交于
-
由 Huon Wilson 提交于
-
- 08 1月, 2015 4 次提交
-
-
由 Flavio Percoco 提交于
-
由 Felix S. Klock II 提交于
To avoid using the feauture, change uses of `box <expr>` to `Box::new(<expr>)` alternative, as noted by the feature gate message. (Note that box patterns have no analogous trivial replacement, at least not in general; you need to revise the code to do a partial match, deref, and then the rest of the match.) [breaking-change]
-
由 Jorge Aparicio 提交于
-
由 Jorge Aparicio 提交于
-
- 07 1月, 2015 5 次提交
-
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
Conflicts: src/librbml/lib.rs src/libserialize/json_stage0.rs src/libserialize/serialize_stage0.rs src/libsyntax/ast.rs src/libsyntax/ext/deriving/generic/mod.rs src/libsyntax/parse/token.rs
-
由 Nick Cameron 提交于
-
由 Niko Matsakis 提交于
parameters on impls must now also appear in the trait ref, self type, or some associated type declared on the impl. This ensures that they are constrianed in some way and that the semantics of the trait system are well-defined (always a good thing). There are three major ways to fix this error: 1. Convert the trait to use associated types; most often the type parameters are not constrained because they are in fact outputs of the impl. 2. Move the type parameters to methods. 3. Add an additional type parameter to the self type or trait so that the unused parameter can appear there. In some cases, it is not possible to fix the impl because the trait definition needs to be changed first (and that may be out of your control). In that case, for the time being, you can opt out of these rules by using `#[old_impl_check]` on the impl and adding a `#![feature(old_impl_check)]` to your crate declaration.
-
由 Nick Cameron 提交于
-
- 06 1月, 2015 3 次提交
-
-
由 Alex Crichton 提交于
-
由 Keegan McAllister 提交于
-
由 Keegan McAllister 提交于
-