-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rollup of 19 pull requests #58348
Rollup of 19 pull requests #58348
Conversation
It is easier and it should be also faster, because `to_ne_bytes` just calls `mem::transmute`.
This is not really significant, accept or reject as you wish. I just want to make sure I understand how the PR process works and I'm doing it right before doing a bigger one for rust-lang#33417.
Update reference of rlibc crate to compiler-builtins crate None
…r=scottmcm Use `to_ne_bytes` for converting IPv4Addr to octets It is easier and it should be also faster, because [`to_ne_bytes`](https://doc.rust-lang.org/std/primitive.u32.html#method.to_ne_bytes) just calls `mem::transmute`.
Tiny expansion to docs for `core::convert`. This is not really significant, accept or reject as you wish. I just want to make sure I understand how the PR process works and that I'm doing it right before doing a bigger one for rust-lang#33417.
MaybeUninit: some docs, rename into_inner -> into_initialized, return &mut from set
Partially HirId-ify rustc Another step towards rust-lang#57578.
Partially HirIdify mir Another step towards rust-lang#57578.
Partially Hiridify typeck Another step towards rust-lang#57578.
Add Cargo.lock automatically adding message If I execute `cargo +nightly fix`, this change always occurs; cc rust-lang#58099 r? @Centril
rustdoc: display sugared return types for async functions Fixes rust-lang#58027.
Add #[must_use] message to Fn* traits This PR adds `#[must_use]` message to `Fn*` traits. Related: rust-lang#57549 r? @estebank
std::sys::unix::stdio: explain why we do into_raw I was quite puzzled why someone would call `into_raw` and then ignore the result.
…isdreavus Cleanup JS a bit r? @QuietMisdreavus
…rochenkov librustc_typeck => 2018 Transitions `librustc_typeck` to Rust 2018; cc rust-lang#58099 TODO: elided_lifetimes_in_paths r? @Centril
…s, r=oli-obk Use `?` in librustc macros
…r=petrochenkov librustc_codegen_ssa => 2018 Transitions `librustc_codegen_ssa` to Rust 2018; cc rust-lang#58099 r? @petrochenkov
miri: give non-generic functions a stable address This makes Miri correctly handle format string parameters despite rust-lang#58320. Matching Miri PR: rust-lang/miri#626 r? @oli-obk
…r=oli-obk operand-to-place copies should never be overlapping This seems to just work (verified with the Miri test suite). r? @oli-obk
When there are multiple filenames, print what got interpreted as filenames I have written code that crafts command lines for rustc, and when I get "multiple input filenames provided" it can be quite hard to figure out where in this long list of arguments the mistake is hiding. Probably I passed an argument to a flag that does not expect an argument, but which flag would that be? This changes the error message to print the first two filenames, to make it easier to debug what is going on.
rpath computation: explain why we pop() I was quite confused by this code until I got a debug log of what is going on.
@bors r+ p=19 |
📌 Commit a5a09e3 has been approved by |
⌛ Testing commit a5a09e3 with merge 591c001e1d0d243c80e4b19a72ae4818efe487e1... |
💔 Test failed - checks-travis |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Caused by #58129. |
Successful merges:
to_ne_bytes
for converting IPv4Addr to octets #57740 (Useto_ne_bytes
for converting IPv4Addr to octets)core::convert
. #57926 (Tiny expansion to docs forcore::convert
.)?
in librustc macros #58313 (Use?
in librustc macros)Failed merges:
r? @ghost