-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 8 pull requests #115326
Rollup of 8 pull requests #115326
Conversation
Having a section for this inspired by the docs for array::IntoIterator
That xref contains the actual documentation for what format! does. It should be very prominent - particularly, more so than the other links.
This reverts commit 6ec570a.
This reverts commit 9de1a47.
it was already unused before, but due to the recursion the compiler did not realize
Do not print `impl<> Foo for &Bar`.
…aber MIR validation: reject in-place argument/return for packed fields As discussed [here](https://rust-lang.zulipchat.com/#narrow/stream/136281-t-opsem/topic/Packed.20fields.20and.20in-place.20function.20argument.2Freturn.20passing).
codegen_llvm/llvm_type: avoid matching on the Rust type This `match` is highly suspicious. Looking at `scalar_llvm_type_at` I think it makes no difference. But if it were to make a difference that would be a huge problem, since it doesn't look through `repr(transparent)`! Cc `@eddyb` `@bjorn3`
More precisely detect cycle errors from type_of on opaque Not sure if this still needs work. Just putting it up for initial impressions, since it seems that a few people are frustrated with the increased error verbosity due to rust-lang#113320. Essentially we introduce a new sub-query for `type_of` specifically for opaques which returns a value that is able to distinguish "has errors" from "due to cycle recovery". Fixes rust-lang#115188 r? `@oli-obk`
Document panic behavior across editions, and improve xrefs This revives (parts of) rust-lang#96518. r? `@scottmcm` Cc `@ijackson`
Revert "Suggest using `Arc` on `!Send`/`!Sync` types" Closes rust-lang#114687. This is a clean revert of rust-lang#88936 + rust-lang#115210. The suggestion to Arc\<{Self}\> when Self does not implement Send is *always* wrong. rust-lang#114842 is considering a way to make a more refined suggestion.
Devacationize oli-obk r? `@oli-obk` `@bors` r+ rollup
…fleLapkin don't use SnapshotVec in Graph implementation, as it looks unused; use Vec instead `Graph` don't use `SnapshotVec` methods, so use simple `Vec` instead?
…rors Tweak output of `to_pretty_impl_header` involving only anon lifetimes Do not print `impl<> Foo for &Bar`.
@bors r+ rollup=never p=8 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 93dd620241 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (4e78abb): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 631.167s -> 631.054s (-0.02%) |
Successful merges:
Arc
on!Send
/!Sync
types" #115311 (Revert "Suggest usingArc
on!Send
/!Sync
types")to_pretty_impl_header
involving only anon lifetimes #115322 (Tweak output ofto_pretty_impl_header
involving only anon lifetimes)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup