- 17 9月, 2016 10 次提交
-
-
由 bors 提交于
Remove variant `MacroRulesTT` of `SyntaxExtension` r? @nrc
-
由 bors 提交于
Rollup of 8 pull requests - Successful merges: #36383, #36424, #36480, #36484, #36505, #36509, #36519, #36521 - Failed merges:
-
由 Jonathan Turner 提交于
Fix language in documentation comment.
-
由 Jonathan Turner 提交于
Add example in AsMut trait documentation Let me know of any changes I should make. r? @GuillaumeGomez
-
由 Jonathan Turner 提交于
Try to support py3 with rustbuild better Annoying to have it fail when you run with `python` only to have to rerun later with `python2`. r? @alexcrichton
-
由 Jonathan Turner 提交于
Default RUST_MIN_STACK to 16MiB for now Temporary(?) workaround to https://github.com/rust-lang/rust/issues/35408. cc @nikomatsakis if you want to veto the idea. r? @EddyB
-
由 Jonathan Turner 提交于
Don't ignore a doc code-block we can compile.
-
由 Jonathan Turner 提交于
doc: make that sound better
-
由 Jonathan Turner 提交于
Tweak std::marker docs Fixes #29361. r? @GuillaumeGomez
-
由 Jonathan Turner 提交于
Update E0049 to new error format Fixes #35210. Part of #35233. r? @jonathandturner
-
- 16 9月, 2016 22 次提交
-
-
由 bors 提交于
a few move-checker improvements This fixes moves out of unions and prohibits moves out of slices (see the individual commits). r? @pnkfelix
-
由 Ariel Ben-Yehuda 提交于
-
由 Ariel Ben-Yehuda 提交于
Moving out of a union is now treated like moving out of its parent type. Fixes #36246
-
由 Ariel Ben-Yehuda 提交于
The wording of RFC #495 enables moves out of slices. Unfortuantely, non-zeroing moves out of slices introduce a very annoying complication: as slices can vary in their length, indexes from the start and end may or may not overlap depending on the slice's exact length, which prevents assigning a particular drop flag for each individual element. For example, in the code ```Rust fn foo<T>(a: Box<[Box<[T]>]>, c: bool) -> T { match (a, c) { (box [box [t, ..], ..], true) => t, (box [.., box [.., t]], false) => t, _ => panic!() } } ``` If the condition is false, we have to drop the first element of `a`, unless `a` has size 1 in which case we drop all the elements of it but the last. If someone comes with a nice way of handling it, we can always re-allow moves out of slices. This is a [breaking-change], but it is behind the `slice_patterns` feature gate and was not allowed until recently.
-
由 Ariel Ben-Yehuda 提交于
-
由 bors 提交于
rustbuild: Fix cross-compiles to MinGW on Linux Closes #36290 Closes #36291
-
由 bors 提交于
Be more specific when type parameter shadows primitive type When a type parameter shadows a primitive type, the error message was non obvious. For example, given the file `file.rs`: ```rust trait Parser<T> { fn parse(text: &str) -> Option<T>; } impl<bool> Parser<bool> for bool { fn parse(text: &str) -> Option<bool> { Some(true) } } fn main() { println!("{}", bool::parse("ok").unwrap_or(false)); } ``` The output was: ```bash % rustc file.rs error[E0308]: mismatched types --> file.rs:7:14 | 7 | Some(true) | ^^^^ expected type parameter, found bool a | = note: expected type `bool` = note: found type `bool` error: aborting due to previous error ``` We now show extra information about the type: ```bash % rustc file.rs error[E0308]: mismatched types --> file.rs:7:14 | 7 | Some(true) | ^^^^ expected type parameter, found bool a | = note: expected type `bool` (type parameter) = note: found type `bool` (bool) error: aborting due to previous error ``` Fixes #35030
-
由 bors 提交于
Add rustc version info (git hash + date) to dist tarball a fix for #32444
-
由 Esteban Küber 提交于
When a type parameter shadows a primitive type, the error message was non obvious. For example, given the file `file.rs`: ```rust trait Parser<T> { fn parse(text: &str) -> Option<T>; } impl<bool> Parser<bool> for bool { fn parse(text: &str) -> Option<bool> { Some(true) } } fn main() { println!("{}", bool::parse("ok").unwrap_or(false)); } ``` The output was: ```bash % rustc file.rs error[E0308]: mismatched types --> file.rs:7:14 | 7 | Some(true) | ^^^^ expected type parameter, found bool | = note: expected type `bool` = note: found type `bool` error: aborting due to previous error ``` We now show extra information about the type: ```bash % rustc file.rs error[E0308]: mismatched types --> file.rs:7:14 | 7 | Some(true) | ^^^^ expected type parameter, found bool | = note: expected type `bool` (type parameter) = note: found type `bool` (bool) error: aborting due to previous error ``` Fixes #35030
-
由 Mark-Simulacrum 提交于
-
由 bors 提交于
rustbuild: Fix dependency tracking with new Cargo The recent Cargo update changed filenames, which broke a lot of incremental rustbuild builds. What it thought were the output files were indeed no longer the output files! (wreaking havoc). This commit updates this to stop guessing filenames of Cargo and just manage stamp files instead.
-
由 Simonas Kazlauskas 提交于
-
由 Jeffrey Seyfried 提交于
-
由 Jeffrey Seyfried 提交于
-
由 Jeffrey Seyfried 提交于
-
由 Jeffrey Seyfried 提交于
-
由 Simonas Kazlauskas 提交于
-
由 bors 提交于
Remove some obsolete code from the compiler
-
由 Keegan McAllister 提交于
Fixes #29361.
-
由 bors 提交于
Add `pub fn ptr_eq(this: &Self, other: &Self) -> bool` to Rc and Arc Servo and Kuchiki have had helper functions doing this for some time.
-
-
由 Simon Sapin 提交于
Servo and Kuchiki have had helper functions doing this for some time.
-
- 15 9月, 2016 8 次提交
-
-
由 bors 提交于
Rollup of 9 pull requests - Successful merges: #36384, #36405, #36425, #36429, #36438, #36454, #36459, #36461, #36463 - Failed merges: #36444
-
由 Manish Goregaokar 提交于
Add checked operation methods to Duration Addresses #35774.
-
由 Manish Goregaokar 提交于
clear obligations-added flag with nested fulfillcx This flag is a debugging measure designed to detect cases where we start a snapshot, create type variables, register obligations involving those type variables in the fulfillment cx, and then have to unroll the snapshot, leaving "dangling type variables" behind. HOWEVER, in some cases the flag is wrong. In particular, we sometimes create a "mini-fulfilment-cx" in which we enroll obligations. As long as this fulfillment cx is fully drained before we return, this is not a problem, as there won't be any escaping obligations in the main cx. So we add a fn to save/restore the flag. Fixes #36053. r? @arielb1
-
由 Manish Goregaokar 提交于
invoke drop glue with a ptr to (data, meta) This is done by creating a little space on the stack. Hokey, but it's the simplest fix I can see, and I am in "kill regressions" mode right now. Fixes #35546 r? @EddyB
-
由 Manish Goregaokar 提交于
Use primitive indexing in slice's Index/IndexMut [T]'s Index implementation is normally not used for indexing, instead the compiler supplied indexing is used. Use the compiler supplied version in Index/IndexMut. This removes an inconsistency: Compiler supplied bound check failures look like this: thread 'main' panicked at 'index out of bounds: the len is 3 but the index is 4' If you convince Rust to use the Index impl for slices, bounds check failure looks like this instead: thread 'main' panicked at 'assertion failed: index < self.len()' The latter is used if you for example use Index generically: ```rust use std::ops::Index; fn foo<T: ?Sized>(x: &T) where T: Index<usize> { &x[4]; } foo(&[1, 2, 3][..]) ```
-
由 Manish Goregaokar 提交于
Assign node ids during macro expansion After this PR, - The `ExtCtxt` can access `resolve`'s `Resolver` through the trait object `ext::base::Resolver`. - The `Resolver` trait object can load macros and replaces today's `MacroLoader` trait object. - The macro expander uses the `Resolver` trait object to resolve macro invocations. - The macro expander assigns node ids and builds the `Resolver`'s `macros_at_scope` map. - This is groundwork for merging import resolution and expansion. - Performance of expansion together with node id assignment improves by ~5%. **EDIT:** Since Github is reordering the commits, here is `git log`: - b54e1e39: Differentiate between monotonic and non-monotonic expansion and only assign node ids during monotonic expansion. - 78c00398: Expand generated test harnesses and macro registries. - f3c2dca3: Remove scope placeholders from the crate root. - c86c8d41: Perform node id assignment and `macros_at_scope` construction during the `InvocationCollector` and `PlaceholderExpander` folds. - 72a63697: Move macro resolution into `librustc_resolve`. - 20b43b23: Rewrite the unit tests in `ext/expand.rs` as a `compile-fail` test. - a9821e16: Refactor `ExtCtxt` to use a `Resolver` instead of a `MacroLoader`. - 60440b22: Refactor `noop_fold_stmt_kind` out of `noop_fold_stmt`. - 50f94f6c: Avoid needless reexpansions. r? @nrc
-
由 Manish Goregaokar 提交于
fix "X is not a member of trait Y" span labels Fixes #36428.
-
由 Manish Goregaokar 提交于
Fix indeterminism in ty::TraitObject representation. Make sure that projection bounds in `ty::TraitObject` are sorted in a way that is stable across compilation sessions and crate boundaries. This PR + moves `DefPathHashes` up into `librustc` so it can be used there to create a stable sort key for `DefId`s, + changes `PolyExistentialProjection::sort_key()` to take advantage of the above, + and removes the unused `PolyProjectionPredicate::sort_key()` and `ProjectionTy::sort_key()` methods. Fixes #36155
-