- 02 10月, 2014 6 次提交
-
-
由 Eduard Burtescu 提交于
-
由 P1start 提交于
Previously it output `partially moved` to eagerly. This updates it to be more accurate and output `collaterally moved` for use of values that were invalidated by moves out of different fields in the same struct. Closes #15630.
-
由 Nick Cameron 提交于
[breaking-change] If you are using slicing syntax you will need to add #![feature(slicing_syntax)] to your crate.
-
由 Nick Cameron 提交于
-
由 P1start 提交于
Closes #17263.
-
由 P1start 提交于
-
- 01 10月, 2014 4 次提交
-
-
由 Florian Hahn 提交于
-
由 Kevin Ballard 提交于
-
由 Kevin Ballard 提交于
Modify ast::ExprMatch to include a new value of type ast::MatchSource, making it easy to tell whether the match was written literally or produced via desugaring. This allows us to customize error messages appropriately.
-
由 Patrick Walton 提交于
This breaks code that looks like: match foo { 1..3 => { ... } } Instead, write: match foo { 1...3 => { ... } } Closes #17295. [breaking-change]
-
- 30 9月, 2014 2 次提交
-
-
由 Nick Cameron 提交于
closes #17392
-
由 Alex Crichton 提交于
-
- 29 9月, 2014 4 次提交
-
-
由 Brian Koropoff 提交于
-
由 Nick Cameron 提交于
-
由 Brian Koropoff 提交于
Also fix an existing compile-fail test which was intended to cover this case. This closes issue #17593
-
由 Andrew Poelstra 提交于
Followup to RFC 57. Fixes #7607 Fixes #8767 Fixes #12729 Fixes #15060
-
- 28 9月, 2014 2 次提交
-
-
由 Steven Fackler 提交于
This removes the ability to use `foo(bar)` style cfgs. Switch them to `foo_bar` or `foo="bar"` instead. [breaking-change]
-
由 Keegan McAllister 提交于
Fixes #17552.
-
- 27 9月, 2014 2 次提交
-
-
由 Piotr Jawniak 提交于
Closes #16465
-
由 Patrick Walton 提交于
in favor of `move`. This breaks code that used `move` as an identifier, because it is now a keyword. Change such identifiers to not use the keyword `move`. Additionally, this breaks code that was counting on by-value or by-reference capture semantics for unboxed closures (behind the feature gate). Change `ref |:|` to `|:|` and `|:|` to `move |:|`. Part of RFC #63; part of issue #12831. [breaking-change]
-
- 25 9月, 2014 9 次提交
-
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
由 Florian Hahn 提交于
-
由 Florian Hahn 提交于
-
由 Jakub Wieczorek 提交于
-
由 Jakub Wieczorek 提交于
-
由 Piotr Czarnecki 提交于
-
- 23 9月, 2014 3 次提交
-
-
由 Patrick Walton 提交于
They will ICE during typechecking if used, because they depend on trait reform. This is part of unboxed closures.
-
由 Patrick Walton 提交于
This breaks code like: struct Foo { ... } pub fn make_foo() -> Foo { ... } Change this code to: pub struct Foo { // note `pub` ... } pub fn make_foo() -> Foo { ... } The `visible_private_types` lint has been removed, since it is now an error to attempt to expose a private type in a public API. In its place a `#[feature(visible_private_types)]` gate has been added. Closes #16463. RFC #48. [breaking-change]
-
由 Victor Berger 提交于
Closes #17185.
-
- 22 9月, 2014 1 次提交
-
-
由 Alex Crichton 提交于
-
- 21 9月, 2014 3 次提交
-
-
由 Colin Davidson 提交于
Closes #12443
-
由 Jakub Wieczorek 提交于
Fixes #17383.
-
由 Jakub Wieczorek 提交于
This is to make sure it hadn't been moved if there are no bindings in any of the arms. Fixes #17385.
-
- 20 9月, 2014 4 次提交
-
-
由 Mike Boutin 提交于
Display an explicit message about items missing after sugared doc comment attributes. References #2789.
-
由 Brian Koropoff 提交于
-
由 Brian Koropoff 提交于
-
由 Alex Crichton 提交于
-