- 24 4月, 2020 12 次提交
-
-
由 marmeladema 提交于
-
由 marmeladema 提交于
-
由 marmeladema 提交于
-
由 bors 提交于
Rollup of 7 pull requests Successful merges: - #70633 (Confusing suggestion on incorrect closing `}`) - #71404 (Don't fuse Chain in its second iterator) - #71408 (Check code blocks tags) - #71442 (Add a "by reference" adaptor for `AllocRef`) - #71446 (Only use read_unaligned in transmute_copy if necessary) - #71470 (Fix doc links) - #71479 (add back Scalar::null_ptr) Failed merges: r? @ghost
-
由 Dylan DPC 提交于
add back Scalar::null_ptr We were a bit overeager with removing this in https://github.com/rust-lang/rust/pull/71005, Miri uses this function quite a bit. The important part is that the `Place::null` methods are gone. :) r? @jonas-schievink @oli-obk Fixes https://github.com/rust-lang/rust/issues/71474
-
由 Dylan DPC 提交于
Fix doc links This fixes a few doc links which were causing `cargo doc` to fail when using `--document-private-items --document-hidden-items` on libstd. Most of the fixes are just escaping '[' and ']' characters in doc comments, and one change actually fixes a doc link.
-
由 Dylan DPC 提交于
Only use read_unaligned in transmute_copy if necessary I've noticed that this causes LLVM to generate poor code on targets that don't support unaligned memory accesses.
-
由 Dylan DPC 提交于
Add a "by reference" adaptor for `AllocRef` Fixes rust-lang/wg-allocators#53 r? @Amanieu
-
由 Dylan DPC 提交于
Check code blocks tags Fixes #71347. Explanations here: I realized recently that it was a common issue to confuse/misspell tags on code blocks. This is actually quite a big issue since it generally ends up in a code blocks being ignored since it's not being considered as a rust one. With this new warning, users will at least be notified about it. PS: some improvements can be done on the error rendering but considering how big the PR already is, I think it's better to do it afterwards. r? @ollie27 cc @rust-lang/rustdoc
-
由 Dylan DPC 提交于
Don't fuse Chain in its second iterator Only the "first" iterator is actually set `None` when exhausted, depending on whether you iterate forward or backward. This restores behavior similar to the former `ChainState`, where it would transition from `Both` to `Front`/`Back` and only continue from that side. However, if you mix directions, then this may still set both sides to `None`, totally fusing the iterator. Fixes #71375 r? @scottmcm
-
由 Dylan DPC 提交于
Confusing suggestion on incorrect closing `}` Compiler returns ``` error: unexpected closing delimiter: `}` --> main.rs:20:1 | 9 | ErrorHandled::Reported => {} | -- this block is empty, you might have not meant to close it temp ... 20 | } | ^ unexpected closing delimiter error: aborting due to previous error ```
-
由 Ralf Jung 提交于
-
- 23 4月, 2020 28 次提交
-
-
由 Tyler Ruckinger 提交于
-
由 Guillaume Gomez 提交于
-
由 Tyler Ruckinger 提交于
-
由 Tyler Ruckinger 提交于
-
由 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
-
由 Guillaume Gomez 提交于
-
由 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
-
由 Guillaume Gomez 提交于
-
由 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 提交于
-
由 Amanieu d'Antras 提交于
-