- 25 4月, 2020 2 次提交
-
-
由 Dylan MacKenzie 提交于
-
由 Dylan MacKenzie 提交于
-
- 23 4月, 2020 35 次提交
-
-
由 bors 提交于
Rollup of 6 pull requests Successful merges: - #71005 (Reading from the return place is fine) - #71198 (Const check/promotion cleanup and sanity assertion) - #71396 (Improve E0308 error message wording again) - #71452 (Remove outdated reference to interpreter snapshotting) - #71454 (Inline some function docs in `core::ptr`) - #71461 (Improve E0567 explanation) Failed merges: r? @ghost
-
由 Dylan DPC 提交于
Improve E0567 explanation r? @Dylan-DPC
-
由 Dylan DPC 提交于
Inline some function docs in `core::ptr` Resolves #64539.
-
由 Dylan DPC 提交于
Remove outdated reference to interpreter snapshotting This should have been a part of #70087. r? @RalfJung
-
由 Dylan DPC 提交于
Improve E0308 error message wording again Hello again, I recently did this PR: #70242 I felt the error message could be further improved, so I made [a post on the Rust community forum](https://users.rust-lang.org/t/looking-for-feedback-on-an-improved-error-message-for-e0308/40004) to ask for feedback. (Also, there were some comments on my original PR that I took into consideration as well.) This PR is my attempt to take all the feedback into account and propose a better and simplified error message that should still be accurate. Its main benefit is having simpler grammar, and hopefully being easier to read and understand. Thanks to everyone who commented and gave feedback, and thank you for taking a look at this PR.
-
由 Dylan DPC 提交于
Const check/promotion cleanup and sanity assertion r? @RalfJung This is just the part of https://github.com/rust-lang/rust/pull/70042#issuecomment-614592765 that does not change behaviour
-
由 Dylan DPC 提交于
Reading from the return place is fine Const eval thinks that reading from local `_0` is UB, but it isn't. `_0` is just a normal local like any other, and codegen handles it that way too. The only special thing is that the `Return` terminator will read from it. I've hit these errors while working on an NRVO pass that can merge other locals with `_0` in https://github.com/rust-lang/rust/pull/71003. r? @oli-obk
-
由 Oliver Scherer 提交于
-
由 Oliver Scherer 提交于
-
由 Oliver Scherer 提交于
-
由 Guillaume Gomez 提交于
-
由 Oliver Scherer 提交于
-
由 Oliver Scherer 提交于
-
由 Oliver Scherer 提交于
This renaming was already done in some modules via import renaming. It's strictly used as a context, and it contains a `TyCtxt`.
-
由 Oliver Scherer 提交于
Fix ui test blessing when a test has an empty stderr file after having had content there before the current changes
-
由 bors 提交于
update Miri Fixes https://github.com/rust-lang/rust/issues/71241 r? @ghost Cc @rust-lang/miri
-
由 bors 提交于
[ConstProp] Use a `BitSet<Local>` instead of `IndexVec<Local, bool>`
-
由 Dylan MacKenzie 提交于
-
由 bors 提交于
Rollup of 5 pull requests Successful merges: - #71256 (Lint must_use on mem::replace) - #71350 (Error code explanation extra check) - #71369 (allow wasm32 compilation of librustc_data_structures/profiling.rs) - #71400 (proc_macro::is_available()) - #71440 (Implement `Copy` for `AllocErr`) Failed merges: r? @ghost
-
由 Dylan MacKenzie 提交于
-
由 Ralf Jung 提交于
-
由 Dylan DPC 提交于
Implement `Copy` for `AllocErr` r? @Amanieu
-
由 Dylan DPC 提交于
proc_macro::is_available() This PR adds `proc_macro::is_available() -> bool` to determine whether proc_macro has been made accessible to the currently running program. The proc_macro crate is only intended for use inside the implementation of procedural macros. All the functions in the crate panic if invoked from outside of a procedural macro, such as from a build script or unit test or ordinary Rust binary. Unfortunately those panics made it impossible for libraries that are designed to support both macro and non-macro use cases (e.g. Syn) to be used from binaries that are compiled with panic=abort. In panic=unwind mode we're able to attempt a proc macro call inside catch_unwind and use libproc_macro's result if it succeeds, otherwise fall back to a non-macro alternative implementation. But in panic=abort there was no way to determine which implementation needs to be used. r? @EddyB attn: @petrochenkov @adetaylor ref: https://github.com/dtolnay/cxx/issues/130
-
由 Dylan DPC 提交于
allow wasm32 compilation of librustc_data_structures/profiling.rs I'm trying to use rustfmt from a wasm app. I ran into this compilation problem https://github.com/rust-lang/rustfmt/issues/4132 and after investigating, it looked like just adjusting a few cfg's. I based it on how measureme added support in https://github.com/rust-lang/measureme/pull/43. My testing on my macbook was just that librustc_data_structures builds now with both: - cargo build - cargo build --target wasm32-unknown-unknown
-
由 Dylan DPC 提交于
Error code explanation extra check r? @Mark-Simulacrum
-
由 Dylan DPC 提交于
Lint must_use on mem::replace This adds a hint on `mem::replace`, "if you don't need the old value, you can just assign the new value directly". This is in similar spirit to the `must_use` on `ManuallyDrop::take`.
-
由 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)
-
由 Tim Diekmann 提交于
-
由 David Tolnay 提交于
-
由 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 3 次提交
-
-
由 Cameron Taggart 提交于
-
由 Cameron Taggart 提交于
Co-Authored-By: Necstatic-morse <ecstaticmorse@gmail.com>
-
由 Dylan DPC 提交于
visit_place_base is just visit_local r? @wesleywiser
-