-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 3 pull requests #132190
Rollup of 3 pull requests #132190
Conversation
…` to `allow` See <rust-lang#132181> for more context.
…iage, r=Mark-Simulacrum Add WASM | WASI | Emscripten groups to triagebot.toml Tracking issue: rust-lang/compiler-team#799 ~~This is blocked on amending the notification group section so that the instructions links point somewhere: rust-lang/rustc-dev-guide#2100
…ck, r=Mark-Simulacrum Document `PartialEq` impl for `OnceLock` Adds documentation to `std::sync::OnceLock`'s `PartialEq` implementation: specifies publicly that `OnceLock`s are compared based on their contents, and nothing else. Created in response to, but not directly related to, rust-lang#131959. ## ne This doesn't create and document `PartialEq::ne`. There's precedent for this in [`RefCell`](https://doc.rust-lang.org/std/cell/struct.RefCell.html#impl-PartialEq-for-RefCell%3CT%3E).
… r=compiler-errors Downgrade `untranslatable_diagnostic` and `diagnostic_outside_of_impl` to `allow` Current implementation of translatable diagnostics infrastructure unfortunately causes some friction for compiler contributors. While we don't have a redesign that causes less friction in place, let's downgrade the internal `untranslatable_diagnostic` and `diagnostic_outside_of_impl` lints so we don't indicate to contributors that they *have* to use the current translation infra. I purposefully left `#[allow(untranslatable_diagnostic)]` and `#[allow(diagnostic_outside_of_impl)]` instances untouched because that seems like unnecessary additional churn. See <rust-lang#132181> for context. r? `@davidtwco` (or wg-diagnostics/compiler)
@bors r+ rollup=never p=3 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: 4d88de2acd In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (9b18a12): 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)This benchmark run did not return any relevant results for this metric. 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: 783.187s -> 784.3s (0.14%) |
Successful merges:
PartialEq
impl forOnceLock
#132019 (DocumentPartialEq
impl forOnceLock
)untranslatable_diagnostic
anddiagnostic_outside_of_impl
toallow
#132182 (Downgradeuntranslatable_diagnostic
anddiagnostic_outside_of_impl
toallow
)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup