- 07 3月, 2015 1 次提交
-
-
由 Keegan McAllister 提交于
This is a hack, but I don't think we can do much better as long as `derive` is running at the syntax expansion phase. If the custom_derive feature gate is enabled, this works with user-defined traits and syntax extensions. Without the gate, you can't use e.g. #[derive_Clone] directly, so this does not change the stable language. This commit also cleans up the deriving code somewhat, and forbids some previously-meaningless attribute syntax. For this reason it's technically a [breaking-change]
-
- 05 3月, 2015 1 次提交
-
-
由 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.
-
- 04 3月, 2015 1 次提交
-
-
由 Piotr Czarnecki 提交于
-
- 03 3月, 2015 1 次提交
-
-
由 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.
-
- 01 3月, 2015 1 次提交
-
-
由 Alan Cutter 提交于
-
- 28 2月, 2015 1 次提交
-
-
由 Jorge Aparicio 提交于
-
- 26 2月, 2015 2 次提交
-
-
由 Alexander Bliskovsky 提交于
-
由 Alexander Bliskovsky 提交于
Closes #22698
-
- 25 2月, 2015 1 次提交
-
-
由 Keegan McAllister 提交于
Fixes #22424.
-
- 23 2月, 2015 2 次提交
-
-
由 lummax 提交于
Update the reference page to the change in #20680.
-
由 Steve Klabnik 提交于
Fixes #22152
-
- 22 2月, 2015 1 次提交
-
-
由 Alexander Chernyakhovsky 提交于
The Rust Reference should include the tuple indexing (using a number as a field) notation; currently it is only available on http://doc.rust-lang.org/std/primitive.tuple.html and not easily searchable.
-
- 19 2月, 2015 1 次提交
-
-
由 Niko Matsakis 提交于
-
- 18 2月, 2015 2 次提交
-
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
- 17 2月, 2015 2 次提交
-
-
由 Manish Goregaokar 提交于
-
由 Steve Klabnik 提交于
Fixes #22386
-
- 16 2月, 2015 1 次提交
-
-
由 Lai Jiangshan 提交于
book/syntax-extensions.html was renamed to book/plugins.html, the link should be also updated. Signed-off-by: NLai Jiangshan <laijs@cn.fujitsu.com>
-
- 14 2月, 2015 3 次提交
-
-
由 Steve Klabnik 提交于
Fixes #19278
-
由 Steve Klabnik 提交于
Fixes #14849
-
由 Steve Klabnik 提交于
This isn't something we want to guarantee.
-
- 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.
-
由 Steve Klabnik 提交于
Fixes #22136
-
- 12 2月, 2015 3 次提交
-
-
由 Nick Sarten 提交于
-
由 Nick Sarten 提交于
Replaced outdated use of the `range(start, end)` function where approriate with `start..end`, and tweaked the examples to compile and run with the latest rust. I also fixed two periphery compile issues in reference.md which were occluding whether there were any new errors created by these changes, so I fixed them.
-
由 Dave Huseby 提交于
-
- 11 2月, 2015 1 次提交
-
-
由 Felix S. Klock II 提交于
-
- 10 2月, 2015 2 次提交
-
-
由 Steve Klabnik 提交于
Fixes #20172
-
由 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]
-
- 09 2月, 2015 1 次提交
-
-
由 Alexander Korolkov 提交于
Update reference.md: - derive() no longer supports Zero trait - derive() now supports Copy trait
-
- 08 2月, 2015 2 次提交
-
-
由 Geoffrey Thomas 提交于
This was correct in the EBNF, but not in the prose (which seems to have been copied-and-pasted from regular string literals).
-
由 Keegan McAllister 提交于
Fixes #21833. [breaking-change]
-
- 04 2月, 2015 3 次提交
-
-
由 Steven Fackler 提交于
This was particularly helpful in the time just after OIBIT's implementation to make sure things that were supposed to be Copy continued to be, but it's now creates a lot of noise for types that intentionally don't want to be Copy.
-
由 Andrea Canciani 提交于
As per rust-lang/rfcs#601, replace `be` with `become` as reserved keyword for tail call optimization.
-
由 Manish Goregaokar 提交于
-
- 03 2月, 2015 1 次提交
-
-
由 Simonas Kazlauskas 提交于
-
- 01 2月, 2015 3 次提交
-
-
由 Sébastien Marie 提交于
-
由 Nick Sarten 提交于
Unicode escapes were changed in [this RFC](https://github.com/rust-lang/rfcs/blob/28aeb3c391c9afd344f124d3a69bdc2a420638b2/text/0446-es6-unicode-escapes.md) to use the ES6 \u{00FFFF} syntax with a variable number of digits from 1-6, eliminating the need for two different syntaxes for unicode literals.
-
由 Dan Yang 提交于
-
- 31 1月, 2015 1 次提交
-
-
由 Tobias Bucher 提交于
Also explain integer fallback to `i32`.
-