- 25 4月, 2020 1 次提交
-
-
由 Mark Rousskov 提交于
-
- 24 4月, 2020 37 次提交
-
-
由 bors 提交于
Replace fragile erroneous const sys Closes #67191 r? @oli-obk
-
由 bors 提交于
Simplify `local_def_id` and `as_local_hir_id` See #70853
-
由 bors 提交于
Rollup of 6 pull requests Successful merges: - #70845 (Make the `structural_match` error diagnostic for const generics clearer) - #71063 (Document unsafety in core::{option, hash}) - #71068 (Stabilize UNICODE_VERSION (feature unicode_version)) - #71426 (fix error code in E0751.md) - #71459 (Add leading 0x to offset in Debug fmt of Pointer) - #71492 (Document unsafety in core::{panicking, alloc::layout, hint, iter::adapters::zip}) Failed merges: r? @ghost
-
由 Dylan DPC 提交于
Document unsafety in core::{panicking, alloc::layout, hint, iter::adapters::zip} Helps with #66219. r? @Mark-Simulacrum do you want to continue reading safety comments? :D
-
由 Dylan DPC 提交于
Add leading 0x to offset in Debug fmt of Pointer Currently the `Debug` format for `Pointer` prints its offset in hexadecimal, for example, `alloc38657819+e2` or `alloc35122748+64`. This PR adds a leading `0x` to the offset, in order to make it apparent that it is indeed a hexadecimal number. This came up during discussion of rust-lang/miri#1354. r? @RalfJung
-
由 Dylan DPC 提交于
fix error code in E0751.md reference: https://github.com/rust-lang/rust/issues/71304
-
由 Dylan DPC 提交于
Stabilize UNICODE_VERSION (feature unicode_version) Tracking issue: #49726 r? @sfackler #71020 changed the definition of `UNICODE_VERSION` just yesterday from a struct to a tuple. Maybe you want to wait some more before stabilizing this constant, on the other hand this is a very small and simple addition. CC @behnam @SimonSapin @Serentty
-
由 Dylan DPC 提交于
Document unsafety in core::{option, hash} Helps with #66219. I think that the part that will need reviewing the most is the `hash/sip.rs` file. r? @LukasKalbertodt (or someone else from the libs team)
-
由 Dylan DPC 提交于
Make the `structural_match` error diagnostic for const generics clearer The previous diagnostic caused confusion (https://github.com/rust-lang/rust/issues/70790), so this changes the message to be closer to the message for using non-`structural_match` constants in patterns, explicitly mentioning `#[derive(PartialEq, Eq)]`. Fixes https://github.com/rust-lang/rust/issues/70790. r? @estebank
-
由 LeSeulArtichaut 提交于
-
由 marmeladema 提交于
-
由 marmeladema 提交于
-
由 marmeladema 提交于
-
由 marmeladema 提交于
-
由 marmeladema 提交于
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
由 LeSeulArtichaut 提交于
Co-Authored-By: NMark-Simulacrum <mark.simulacrum@gmail.com>
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
Avoid exercising unevaluated constants and go straight to visit the blocks.
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
由 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 提交于
-
由 LeSeulArtichaut 提交于
Co-authored-by: NMark-Simulacrum <mark.simulacrum@gmail.com>
-
- 23 4月, 2020 2 次提交
-
-
由 Tyler Ruckinger 提交于
-
由 Guillaume Gomez 提交于
-