- 23 4月, 2020 10 次提交
-
-
由 Dylan MacKenzie 提交于
-
由 Dylan MacKenzie 提交于
...instead of a `LockGuard` which means the lock is held for longer than necessary.
-
由 Dylan MacKenzie 提交于
There is no `Arc::map` equivalent to `LockGuard::map`
-
由 bors 提交于
Remove `BodyAndCache` ...returning to the original approach using interior mutability within `Body`. This simplifies the API at the cost of some uncontended mutex locks when the parallel compiler is enabled. The current API requires you to either have a mutable reference to `Body` (`&mut BodyAndCache`), or to compute the predecessor graph ahead of time by creating a `ReadOnlyBodyAndCache`. This is not a good fit for, e.g., the dataflow framework, which 1. does not mutate the MIR 2. only sometimes needs the predecessor graph (for backward dataflow problems)
-
由 bors 提交于
Rollup of 4 pull requests Successful merges: - #71280 (Miri: mplace_access_checked: offer option to force different alignment on place) - #71336 (Exhaustively match on `{Statement,Terminator}Kind` during const checking) - #71370 (Added detailed error code explanation for issue E0696 in Rust compiler.) - #71401 (visit_place_base is just visit_local) Failed merges: r? @ghost
-
由 Dylan MacKenzie 提交于
...with a single one to `predecessors`. `predecessors_for` requires taking the lock/incrementing the `RefCell` once each call.
-
由 Dylan MacKenzie 提交于
-
由 Dylan MacKenzie 提交于
-
由 Dylan MacKenzie 提交于
-
由 Dylan MacKenzie 提交于
-
- 22 4月, 2020 30 次提交
-
-
由 Dylan DPC 提交于
visit_place_base is just visit_local r? @wesleywiser
-
由 Dylan DPC 提交于
Added detailed error code explanation for issue E0696 in Rust compiler. Added proper error explanation for issue E0696 in the Rust compiler. Error Code E0696 Sub Part of Issue #61137 r? @GuillaumeGomez
-
由 Dylan DPC 提交于
Exhaustively match on `{Statement,Terminator}Kind` during const checking This adds a pre-monomorphization error for inline assembly in a const context as well. r? @oli-obk
-
由 Dylan DPC 提交于
Miri: mplace_access_checked: offer option to force different alignment on place Required to solve https://github.com/rust-lang/miri/issues/1339 in https://github.com/rust-lang/miri/pull/1348. r? @oli-obk
-
由 bors 提交于
Alphabetize `-C` and `-Z` options Because it will make it much easier to find options that way. r? @petrochenkov
-
由 Nicholas Nethercote 提交于
-
由 Nicholas Nethercote 提交于
-
由 Nicholas Nethercote 提交于
In the code, test, and docs, because it makes it much easier to find things. Other than adding the comments about alphabetical order, this commit only moves things around.
-
由 bors 提交于
Rollup of 6 pull requests Successful merges: - #70970 (Detect mistyped associated consts in `Instance::resolve`.) - #71203 (Correct await span for async-await error reporting) - #71214 (Add error code for inner doc error) - #71337 (Moving all rustdoc-ui tests to check-pass) - #71412 (Clarify unused_doc_comments note on macro invocations) - #71414 (More diagnostic items for Clippy usage) Failed merges: r? @ghost
-
由 Ralf Jung 提交于
-
由 Dylan DPC 提交于
More diagnostic items for Clippy usage This adds a couple of more diagnostic items to be used in Clippy. I chose these particular ones because they were the types which we seem to check for the most in Clippy. I'm not sure if the `cfg_attr(not(test))` is needed, but it was also used for `Vec` and a few other types. cc https://github.com/rust-lang/rust-clippy/issues/5393 r? @Manishearth
-
由 Dylan DPC 提交于
Clarify unused_doc_comments note on macro invocations The previous error message used to say: <pre> /// doc ^^^^^^^ rustdoc does not generate documentation for <b>macros</b> </pre> Obviously we do generate documentation for macros, such as https://docs.rs/bitflags/1.2.1/bitflags/macro.bitflags.html. It's only macro invocations that don't get their own docs. This PR updates the message to say "rustdoc does not generate documentation for <b>macro invocations</b>". I observe that prior to #69084 this used to say "rustdoc does not generate documentation for **macro expansions**", as implemented originally in #57882. I don't have a preference between those but I made the commit before looking up the history. r? @Manishearth attn: @yaahc @euclio
-
由 Dylan DPC 提交于
Moving all rustdoc-ui tests to check-pass These were all build-pass before and don't seem to need it. Helps with #62277 <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/rust-lang/rust/71337) <!-- Reviewable:end -->
-
由 Dylan DPC 提交于
Add error code for inner doc error r? @Dylan-DPC cc @oli-obk
-
由 Dylan DPC 提交于
Correct await span for async-await error reporting Closes #71137 r? @tmandry
-
由 Dylan DPC 提交于
Detect mistyped associated consts in `Instance::resolve`. *Based on #71049 to prevent redundant/misleading downstream errors.* Fixes #70942 by refusing to resolve an associated `const` if it doesn't have the same type in the `impl` that it does in the `trait` (which we assume had errored, and `delay_span_bug` guards against bugs).
-
由 Guillaume Gomez 提交于
-
由 Guillaume Gomez 提交于
-
由 bors 提交于
Add `-Cbitcode-in-rlib`. This is a cut-down version of #70458 that gets the compile-time wins. r? @alexcrichton
-
由 Philipp Hansch 提交于
This adds a couple of more diagnostic items to be used in Clippy. I chose these particular ones because they were the types which we seem to check for the most in Clippy. I'm not sure if the `cfg_attr(not(test))` is needed, but it was also used for `Vec` and a few other types.
-
由 Nicholas Nethercote 提交于
So that the rlibs will work with both LTO and non-LTO builds.
-
由 Nicholas Nethercote 提交于
-
由 Nicholas Nethercote 提交于
It defaults to true, but Cargo will set this to false whenever it can to reduce compile times.
-
由 Nicholas Nethercote 提交于
This comment wasn't supposed to have landed.
-
由 David Tolnay 提交于
-
由 bors 提交于
Rollup of 7 pull requests Successful merges: - #70998 (Suggest `-> impl Trait` and `-> Box<dyn Trait>` on fn that doesn't return) - #71236 (Remove unused rustc_serialize::hex module) - #71366 (Use assoc int consts3) - #71372 (Fix #! (shebang) stripping account space issue) - #71384 (Fix stage0.txt version number comment) - #71390 (Fix incorrect description of E0690) - #71399 (Clean up E0554 explanation) Failed merges: r? @ghost
-
由 csmoe 提交于
-
由 Yuki Okushi 提交于
Clean up E0554 explanation r? @Dylan-DPC
-
由 Yuki Okushi 提交于
Fix incorrect description of E0690 r? @steveklabnik
-
由 Yuki Okushi 提交于
Fix stage0.txt version number comment r? @Mark-Simulacrum
-