-
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 9 pull requests #100740
Rollup of 9 pull requests #100740
Conversation
…safe_op_in_unsafe_fn
Co-authored-by: Léo Lanteri Thauvin <leseulartichaut@gmail.com>
Module is completed because it doesn’t have any diagnostics
…-drop-is-bad, r=TaKO8Ki Do not allow `Drop` impl on foreign fundamental types `Drop` should not be implemented on `Pin<T>` even if `T` is local. This does not trigger regular orphan rules is because `Pin` is `#[fundamental]`... but we don't allow specialized `Drop` impls anyways, so these rules are not sufficient to prevent this impl on stable. Let's just choose even stricter rules, since we shouldn't be implementing `Drop` on a foreign ADT ever. Fixes rust-lang#99575
…n, r=jackh726 never consider unsafe blocks unused if they would be required with deny(unsafe_op_in_unsafe_fn) Judging from rust-lang#71668 (comment) the consensus nowadays seems to be that we should never consider an unsafe block unused if it was required with `deny(unsafe_op_in_unsafe_fn)`, no matter whether that lint is actually enabled or not. So let's adjust rustc accordingly. The first commit does the change, the 2nd does some cleanup.
…enkov make NOP dyn casts not require anything about the vtable As suggested [on Zulip](https://rust-lang.zulipchat.com/#narrow/stream/144729-t-types/topic/dyn-upcasting.20stabilization/near/292151439). This matches what the codegen backends already do, and what Miri did do until rust-lang#99420 when I made it super extra paranoid.
Cleanup rustdoc themes This PR continues our work to simplify the rustdoc themes by relying more on CSS variables. Interestingly enough, this time it allowed me to realize that we were having a lot of different colors for borders even though the difference is unnoticeable. I used this opportunity to unify them. The live demo is [here](https://rustdoc.crud.net/imperio/cleanup-themes/std/index.html). r? `@jsha`
…ion, r=tmiasko Only check the `DefId` for the recursion check in MIR inliner. The current history check compares `Instance`s, so it cannot detect cases of polymorphic recursion where `Substs` change. This PR makes it so we only compare `DefId`s, ignoring any change in `Substs`. According to rust-lang#100522 (comment), in practice only very few inlining decisions change. Fixes rust-lang#100476
Manually implement Debug for ImportKind. This avoids crashing due to an infinite loop when running with `RUSTC_LOG=rustc_resolve`.
Don't fix builtin index when Where clause is found Where clause shadows blanket impl for `Index` which causes normalization to not occur, which causes ICE to happen when we typeck. r? `@compiler-errors` Fixes rust-lang#91633
…pe-ir, r=compiler-errors Add diagnostics lints to `rustc_type_ir` module Module is complete. It doesn’t have any diagnostics.
…1, r=jsha rustdoc: count deref and non-deref as same set of used methods Fixes rust-lang#100679
@bors r+ rollup=never p=5 |
⌛ Testing commit ecd2885 with merge 76bd100bd3b09a5592c1b9bf3b1d70d386b8617f... |
💥 Test timed out |
@bors retry |
☀️ Test successful - checks-actions |
Tested on commit rust-lang/rust@e1b28cd. Direct link to PR: <rust-lang/rust#100740> 💔 miri on windows: test-pass → test-fail (cc @RalfJung @oli-obk). 💔 miri on linux: test-pass → test-fail (cc @RalfJung @oli-obk).
📌 Perf builds for each rolled up PR: In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (e1b28cd): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
Successful merges:
Drop
impl on foreign fundamental types #99576 (Do not allowDrop
impl on foreign fundamental types)DefId
for the recursion check in MIR inliner. #100522 (Only check theDefId
for the recursion check in MIR inliner.)rustc_type_ir
module #100721 (Add diagnostics lints torustc_type_ir
module)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup