- 14 12月, 2017 2 次提交
-
-
由 Jeffrey Seyfried 提交于
-
由 Jeffrey Seyfried 提交于
-
- 13 12月, 2017 18 次提交
-
-
由 bors 提交于
macros: hygienize use of `core`/`std` in builtin macros Today, if a builtin macro wants to access an item from `core` or `std` (depending `#![no_std]`), it generates `::core::path::to::item` or `::std::path::to::item` respectively (c.f. `fn std_path()` in `libsyntax/ext/base.rs`). This PR refactors the builtin macros to instead always emit `$crate::path::to::item` here. That is, the def site of builtin macros is taken to be in `extern crate core;` or `extern crate std;`. Since builtin macros are macros 1.0 (i.e. mostly unhygienic), changing the def site can only effect the resolution of `$crate`. r? @nrc
-
由 bors 提交于
Record all imports (`use`, `extern crate`) in the crate metadata This PR adds non-`pub` `use` and `extern crate` imports in the crate metadata since hygienic macros invoked in other crates may use them. We already include all other non-`pub` items in the crate metadata. This improves import suggestions in some cases. Fixes #42337. r? @nrc
-
由 Jeffrey Seyfried 提交于
-
由 bors 提交于
Implement impl Trait lifetime elision Fixes #43396. There's one weird ICE in the interaction with argument-position `impl Trait`. I'm still debugging it-- I've left a test for it commented out with a FIXME. Also included a FIXME to ensure that `impl Trait` traits are caught under the lint in https://github.com/rust-lang/rust/issues/45992. r? @nikomatsakis
-
由 bors 提交于
Resolve absolute paths as extern under a feature flag cc https://github.com/rust-lang/rust/issues/44660 r? @nikomatsakis
-
由 bors 提交于
Ignore `unsopported constant expr` error Fixes #46553
-
由 Jeffrey Seyfried 提交于
-
由 Jeffrey Seyfried 提交于
-
由 Vadim Petrochenkov 提交于
-
由 Vadim Petrochenkov 提交于
-
由 bors 提交于
Rollup of 4 pull requests - Successful merges: #46668, #46672, #46691, #46694 - Failed merges:
-
由 kennytm 提交于
Temporarily use the old Travis image. Use it until travis-ci/travis-ci#8891 is fixed. (See also https://blog.travis-ci.com/2017-12-12-new-trusty-images-q4-launch) r? @aidanhs
-
由 kennytm 提交于
Fix return value of `LLVMRustMetadataAsValue` `LLVMRustMetadataAsValue` would previously return `void`, despite the corresponding Rust function expecting to return a `ValueRef`.
-
由 kennytm 提交于
Fix type filter in rustdoc js Fixes #46612. r? @QuietMisdreavus
-
由 kennytm 提交于
Fix mobile doc style and improve search bar Fixes #46593. r? @QuietMisdreavus
-
由 kennytm 提交于
Use it until travis-ci/travis-ci#8891 is fixed.
-
由 Taylor Cramer 提交于
-
由 varkor 提交于
`LLVMRustMetadataAsValue` would previously return `void`, despite the corresponding Rust function expecting to return a `ValueRef`.
-
- 12 12月, 2017 20 次提交
-
-
由 bors 提交于
Add `std::fmt::Pointer` implementation for `AtomicPtr` Resolves #29212.
-
由 bors 提交于
Rename never_type_impls gate We no longer need a separately-named `never_type_impls` gate thanks to https://github.com/rust-lang/rust/issues/43089.
-
由 bors 提交于
Remove armv5te target from dist-various-1 Reverts https://github.com/rust-lang/rust/pull/46498 I must have made some mistake when I tested that commit and thought armv5te target worked. but testing it now the produced binaries segfaults (https://github.com/rust-lang/rust/pull/46498#issuecomment-350599233). I tried using crosstool-ng and buildroot toolchain (for armv5te) but the produced binaries also segfaults. Maybe there is a issue with the target, but I cannot investigate it any further. I think the best for now is not to distribute the armv5te target. I'm sorry for what happened.
-
由 bors 提交于
MIR borrowck: error message confuses locals and temporaries Fixes #46471 and fixes #46472 (see [this Gitter comment](https://gitter.im/rust-impl-period/WG-compiler-nll?at=5a2d5cb53ae2aa6b3facf0c2)). r? @arielb1
-
由 Andrew Cann 提交于
-
由 bors 提交于
Mark ascii methods on primitive types stable in 1.23.0 not 1.21.0. The ascii_methods_on_intrinsics feature stabilization didn't land in time for 1.21.0. Update the annotation so the documentation is correct about when these methods became available.
-
由 bors 提交于
move `resolve_lifetimes` into a proper query Now that we made `resolve_lifetimes` into a query, elision errors no longer abort compilation, which affects some tests. Also, remove `dep_graph_crosscontaminate_tables` -- there is no a path in the dep-graph, though red-green handles it. The same scenario is (correctly) tested by issue-42602.rs in any case. r? @michaelwoerister
-
由 Marco A L Barbosa 提交于
Reverts https://github.com/rust-lang/rust/pull/46498 I must have made some mistake when I tested that commit and thought armv5te target worked. but testing it now the produced binaries segfaults (https://github.com/rust-lang/rust/pull/46498#issuecomment-350599233). I tried using crosstool-ng and buildroot toolchain (for armv5te) but the produced binaries also segfaults. Maybe there is a issue with the target, but I cannot investigate it any further. I think the best for now is not to distribute the armv5te target. I'm sorry for what happened.
-
由 Guillaume Gomez 提交于
-
由 David Wood 提交于
-
由 David Wood 提交于
-
由 Guillaume Gomez 提交于
-
由 bors 提交于
Resolve type on return type suggestion Partially address #45871.
-
由 Niko Matsakis 提交于
-
由 David Wood 提交于
-
由 David Wood 提交于
-
由 David Wood 提交于
-
由 David Wood 提交于
-
由 David Wood 提交于
-
由 bors 提交于
Clean up the MIR borrowck code I want to avoid the new code to start with so much technical debt. r? @nikomatsakis
-