Rollup of 12 pull requests by JonathanBrouwer · Pull Request #154117 · rust-lang/rust

JonathanBrouwer · 2026-03-19T21:52:36Z

Successful merges:

sess: -Zbranch-protection is a target modifier #152909 (sess: -Zbranch-protection is a target modifier)
impl restriction lowering #153556 (impl restriction lowering)
Don't emit rustdoc missing_doc_code_examples lint on impl items #154048 (Don't emit rustdoc missing_doc_code_examples lint on impl items)
bootstrap: Optionally print a backtrace if a command fails #153992 (bootstrap: Optionally print a backtrace if a command fails)
two smaller feature cleanups #154019 (two smaller feature cleanups)
tests: Activate must_not_suspend test for MutexGuard dropped before await #154059 (tests: Activate must_not_suspend test for MutexGuard dropped before await)
Rewrite query_ensure_result. #154075 (Rewrite query_ensure_result.)
Updates derive_where and removes workaround #154082 (Updates derive_where and removes workaround)
Preserve braces around self in use tree pretty printing #154084 (Preserve braces around self in use tree pretty printing)
Insert space after float literal ending with . in pretty printer #154086 (Insert space after float literal ending with . in pretty printer)
Fix whitespace after fragment specifiers in macro pretty printing #154087 (Fix whitespace after fragment specifiers in macro pretty printing)
tests: Add regression test for async closures involving HRTBs #154109 (tests: Add regression test for async closures involving HRTBs)

`-Zbranch-protection` only makes sense if the entire crate graph has the option set, otherwise the security properties that branch protection provides won't be effective. This flag is unstable so I don't think this warrants an MCP.

…wait The test pass in `nightly-2023-09-24` but fail in `nightly-2023-09-23`: $ rustc +nightly-2023-09-23 --edition 2018 tests/ui/lint/must_not_suspend/mutex-guard-dropped-before-await.rs error: `MutexGuard` held across a suspend point, but should not be --> tests/ui/lint/must_not_suspend/mutex-guard-dropped-before-await.rs:13:9 | 13 | let lock = foo.lock().unwrap(); | ^^^^ ... 18 | bar().await; | ----- the value is held across this suspend point |

It currently uses chaining which is concise but hard to read. There are up to four implicit matches occurring after the call to `execute_query_fn`. - The first `map` on `Option<Erased<Result<T, ErrorGuaranteed>>>`. - The second `map` on `Option<Result<T, ErrorGuaranteed>>`. - The third `map` on `Result<T, ErrorGuaranteed>`. - The `unwrap_or` on `Option<Result<(), ErrorGuaranteed>>`. This commit rewrites it to use at most two matches. - An explicit match on `Option<Erased<Result<T, ErrorGuaranteed>>>`. - An explicit match on `Result<T, ErrorGuaranteed>`. This is easier to read. It's also more efficient, though the code isn't hot enough for that to matter.

The AST pretty printer strips braces from single-item `use` sub-groups, simplifying `use foo::{Bar}` to `use foo::Bar`. However, when the single item is `self`, this produces `use foo::self` which is not valid Rust (E0429) — the grammar requires `use foo::{self}`. This affects both `stringify!` and `rustc -Zunpretty=expanded`, causing `cargo expand` output to be unparseable when a crate uses `use path::{self}` imports (a common pattern in the ecosystem). The fix checks whether the single nested item's path starts with `self` before stripping braces. If so, the braces are preserved. Signed-off-by: Andrew V. Teylu <andrew.teylu@vector.com>

When a macro-generating-macro captures fragment specifier tokens (like `$x:ident`) as `tt` metavariables and replays them before a keyword (like `where`), the pretty printer concatenates them into an invalid fragment specifier (e.g. `$x:identwhere` instead of `$x:ident where`). This happens because `tt` captures preserve the original token spacing. When the fragment specifier name (e.g. `ident`) was originally the last token before a closing delimiter, it retains `JointHidden` spacing. The `print_tts` function only checks `space_between` for `Spacing::Alone` tokens, so `JointHidden` tokens skip the space check entirely, causing adjacent identifier-like tokens to merge. The fix adds a check in `print_tts` to insert a space between adjacent identifier-like tokens (identifiers and keywords) regardless of the original spacing, preventing them from being concatenated into invalid tokens. This is similar to the existing `space_between` mechanism that prevents token merging for `Spacing::Alone` tokens, extended to also handle `Joint`/`JointHidden` cases where two identifier-like tokens would merge. Signed-off-by: Andrew V. Teylu <andrew.teylu@vector.com>

The pretty printer was collapsing unsuffixed float literals (like `0.`) with adjacent dot tokens, producing ambiguous or invalid output: - `0. ..45.` (range) became `0...45.` - `0. ..=360.` (inclusive range) became `0...=360.` - `0. .to_string()` (method call) became `0..to_string()` The fix inserts a space after an unsuffixed float literal ending with `.` when it appears as the start expression of a range operator or the receiver of a method call or field access, preventing the trailing dot from merging with the following `.`, `..`, or `..=` token. This is skipped when the expression is already parenthesized, since the closing `)` naturally provides separation. Signed-off-by: Andrew V. Teylu <andrew.teylu@vector.com>

I suspect the original code had several issues. The last one that made the code compile entered `nightly-2024-02-11`. The code fails to build with `nightly-2024-02-10`: $ rustc +nightly-2024-02-10 --edition 2018 tests/ui/async-await/async-closures/unifying-function-types-involving-hrtb.rs error[E0277]: expected a `FnOnce(&u8)` closure, found `{coroutine-closure@tests/ui/async-await/async-closures/unifying-function-types-involving-hrtb.rs:31:9: 31:30}` --> tests/ui/async-await/async-closures/unifying-function-types-involving-hrtb.rs:31:9 | 31 | foo(async move | f: &u8 | { *f }); | --- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected an `FnOnce(&u8)` closure, found `{coroutine-closure@tests/ui/async-await/async-closures/unifying-function-types-involving-hrtb.rs:31:9: 31:30}` | | | required by a bound introduced by this call | (Note that you must add `#![feature(async_closure)]` to test with such old nightlies, since they are from before stabilization of async closures.) This was probably fixed by 3bb384a.

…-modifier, r=jackh726 sess: `-Zbranch-protection` is a target modifier `-Zbranch-protection` only makes sense if the entire crate graph has the option set, otherwise the security properties that branch protection provides won't be effective - hence a target modifier. This flag is unstable so I don't think this warrants an MCP.

@Urgau

…wering, r=petrochenkov `impl` restriction lowering This PR is linked to a [GSoC proposal](https://github.com/rust-lang/google-summer-of-code?tab=readme-ov-file#implementing-impl-and-mut-restrictions) and is part of the progress toward implementing `impl` restrictions proposed in [RFC 3323](https://rust-lang.github.io/rfcs/3323-restrictions.html). This PR implements path resolution for `impl` restrictions. The resolution is performed in `rustc_resolve/src/late.rs` using `smart_resolve_path`. This PR also checks whether the restricted module or crate is an ancestor. If it is not, it emits a restriction-specific counterpart to visibility’s `AncestorOnly` error. r? @Urgau cc @jhpratt

@lolbinarycat

…amples-improvement, r=lolbinarycat Don't emit rustdoc `missing_doc_code_examples` lint on impl items @lolbinarycat realized in [this comment](rust-lang#153964 (comment)) that we weren't testing some cases for the `missing_doc_code_examples` lint. Turns out that it was not handling this case well. =D So in short: `missing_doc_code_examples` lint should not be emitted on impl items and this PR fixes that. r? @lolbinarycat

… r=jieyouxu,kobzol bootstrap: Optionally print a backtrace if a command fails I found this quite useful for debugging why a command was failing eagerly (it turns out that `.delay_failure()` is ignored if `fail_fast` is enabled).

two smaller feature cleanups Remove an unneeded feature gate for a private macro and sort the used features correctly by whether they are language or library features.

…ooeo tests: Activate `must_not_suspend` test for `MutexGuard` dropped before `await` After bisect it turns out that the test passes in `nightly-2023-09-24` but fails in `nightly-2023-09-23`: $ rustc +nightly-2023-09-23 --edition 2018 tests/ui/lint/must_not_suspend/mutex-guard-dropped-before-await.rs error: `MutexGuard` held across a suspend point, but should not be --> tests/ui/lint/must_not_suspend/mutex-guard-dropped-before-await.rs:13:9 | 13 | let lock = foo.lock().unwrap(); | ^^^^ ... 18 | bar().await; | ----- the value is held across this suspend point | That leaves us with <details> <summary>git log e4133ba..13e6f24 --no-merges --oneline </summary> bffb346 Make test more robust to opts. 44ac8dc Remove GeneratorWitness and rename GeneratorWitnessMIR. 855a75b Remove useless wrapper. baa64b0 Remove dead error code. 6aa1268 Bless clippy. d989e14 Bless mir-opt 211d2ed Bless tests. 286502c Enable drop_tracking_mir by default. a626caa Revert duplication of tests. ff03204 Fold lifetimes before substitution. 9450b75 Do not construct def_path_str for MustNotSuspend. 58ef3a0 diagnostics: simpler 83556 handling by bailing out 79d6853 Check types live across yields in generators too c21867f Check that closure's by-value captures are sized d3dea30 Point at cause of expectation of `break` value when possible 4ed4913 Merge `ExternProviders` into the general `Providers` struct 2ba911c Have a single struct for queries and hook 9090ed8 Fix test on targets with crt-static default 5db9a5e Update cargo 9defc97 Add tracing instrumentation, just like queries automatically add it 2157f31 Add a way to decouple the implementation and the declaration of a TyCtxt method. d5ec9af Add test to guard against VecDeque optimization regression 3799af3 diagnostics: avoid mismatch between variance index and hir generic 34c248d compiletest: load supports-xray from target spec 64e27cb compiletest: load supported sanitizers from target spec bc7bb3c compiletest: use builder pattern to construct Config in tests </details> of which 286502c (rust-lang#107421) seems most likely. I can't find an existing test except the "inactive" one, so let's simply activate it. Closes rust-lang#89562 which is where the activated test comes from. The test was originally added in rust-lang#89826. Tracking issue: - rust-lang#83310

@Zalathar

…esult, r=Zalathar Rewrite `query_ensure_result`. It currently uses chaining which is concise but hard to read. There are up to four implicit matches occurring after the call to `execute_query_fn`. - The first `map` on `Option<Erased<Result<T, ErrorGuaranteed>>>`. - The second `map` on `Option<Result<T, ErrorGuaranteed>>`. - The third `map` on `Result<T, ErrorGuaranteed>`. - The `unwrap_or` on `Option<Result<(), ErrorGuaranteed>>`. This commit rewrites it to use at most two matches. - An explicit match on `Option<Erased<Result<T, ErrorGuaranteed>>>`. - An explicit match on `Result<T, ErrorGuaranteed>`. This is easier to read. It's also more efficient, though the code isn't hot enough for that to matter. r? @Zalathar

Updates derive_where and removes workaround Updates dependency on `derive-where` that fixes issue ModProg/derive-where#136 and removes the following workaround: ``` // FIXME(derive-where#136): Need to use separate `derive_where` for // `Copy` and `Ord` to prevent the emitted `Clone` and `PartialOrd` // impls from incorrectly relying on `T: Copy` and `T: Ord`. ``` r? lcnr

Preserve braces around `self` in use tree pretty printing The AST pretty printer strips braces from single-item `use` sub-groups, simplifying `use foo::{Bar}` to `use foo::Bar`. However, when the single item is `self`, this produces `use foo::self` which is not valid Rust (E0429) — the grammar requires `use foo::{self}`. This affects both `stringify!` and `rustc -Zunpretty=expanded`, causing `cargo expand` output to be unparseable when a crate uses `use path::{self}` imports (a common pattern in the ecosystem). The fix checks whether the single nested item's path starts with `self` before stripping braces. If so, the braces are preserved. ## Example **before** (`rustc 1.96.0-nightly (3b1b0ef 2026-03-11)`): ```rust #![feature(prelude_import)] //@ pp-exact //@ edition:2021 #![allow(unused_imports)] extern crate std; #[prelude_import] use std::prelude::rust_2021::*; // Braces around `self` must be preserved, because `use foo::self` is not valid Rust. use std::io::self; use std::fmt::{self, Debug}; fn main() {} ``` **after** (this branch): ```rust #![feature(prelude_import)] //@ pp-exact //@ edition:2021 #![allow(unused_imports)] extern crate std; #[prelude_import] use std::prelude::rust_2021::*; // Braces around `self` must be preserved, because `use foo::self` is not valid Rust. use std::io::{self}; use std::fmt::{self, Debug}; fn main() {} ``` Notice the `use std::io::self` (invalid, E0429) in the before becomes `use std::io::{self}` in the after.

…ivooeo Insert space after float literal ending with `.` in pretty printer The pretty printer was collapsing unsuffixed float literals (like `0.`) with adjacent dot tokens, producing ambiguous or invalid output: - `0. ..45.` (range) became `0...45.` - `0. ..=360.` (inclusive range) became `0...=360.` - `0. .to_string()` (method call) became `0..to_string()` The fix inserts a space after an unsuffixed float literal ending with `.` when it appears as the start expression of a range operator or the receiver of a method call or field access, preventing the trailing dot from merging with the following `.`, `..`, or `..=` token. This is skipped when the expression is already parenthesized, since the closing `)` naturally provides separation. ## Example **before** (`rustc 1.96.0-nightly (3b1b0ef 2026-03-11)`): ```rust #![feature(prelude_import)] #![no_std] extern crate std; #[prelude_import] use ::std::prelude::rust_2015::*; //@ pp-exact fn main() { let _ = 0...45.; let _ = 0...=360.; let _ = 0...; let _ = 0..to_string(); } ``` **after** (this branch): ```rust #![feature(prelude_import)] #![no_std] extern crate std; #[prelude_import] use ::std::prelude::rust_2015::*; //@ pp-exact fn main() { let _ = 0. ..45.; let _ = 0. ..=360.; let _ = 0. ..; let _ = 0. .to_string(); } ``` Notice `0...45.` (ambiguous — looks like deprecated `...` inclusive range) becomes `0. ..45.` (clear: float `0.` followed by range `..`). Similarly `0..to_string()` (parsed as range) becomes `0. .to_string()` (method call on float).

…space, r=Kivooeo Fix whitespace after fragment specifiers in macro pretty printing When a macro-generating-macro captures fragment specifier tokens (like `$x:ident`) as `tt` metavariables and replays them before a keyword (like `where`), the pretty printer concatenates them into an invalid fragment specifier (e.g. `$x:identwhere` instead of `$x:ident where`). This happens because `tt` captures preserve the original token spacing. When the fragment specifier name (e.g. `ident`) was originally the last token before a closing delimiter, it retains `JointHidden` spacing. The `print_tts` function only checks `space_between` for `Spacing::Alone` tokens, so `JointHidden` tokens skip the space check entirely, causing adjacent identifier-like tokens to merge. The fix adds a check in `print_tts` to insert a space between adjacent identifier-like tokens (identifiers and keywords) regardless of the original spacing, preventing them from being concatenated into invalid tokens. This is similar to the existing `space_between` mechanism that prevents token merging for `Spacing::Alone` tokens, extended to also handle `Joint`/`JointHidden` cases where two identifier-like tokens would merge. ## Example **before** (`rustc 1.96.0-nightly (3b1b0ef 2026-03-11)`): ```rust #![feature(prelude_import)] #![no_std] extern crate std; #[prelude_import] use ::std::prelude::rust_2015::*; //@ pretty-mode:expanded //@ pp-exact:macro-fragment-specifier-whitespace.pp // Test that fragment specifier names in macro definitions are properly // separated from the following keyword/identifier token when pretty-printed. // This is a regression test for a bug where `$x:ident` followed by `where` // was pretty-printed as `$x:identwhere` (an invalid fragment specifier). macro_rules! outer { ($d:tt $($params:tt)*) => { #[macro_export] macro_rules! inner { ($($params)* where $d($rest:tt)*) => {}; } }; } #[macro_export] macro_rules! inner { ($x:identwhere $ ($rest : tt)*) => {}; } fn main() {} ``` **after** (this branch): ```rust #![feature(prelude_import)] #![no_std] extern crate std; #[prelude_import] use ::std::prelude::rust_2015::*; //@ pretty-mode:expanded //@ pp-exact:macro-fragment-specifier-whitespace.pp // Test that fragment specifier names in macro definitions are properly // separated from the following keyword/identifier token when pretty-printed. // This is a regression test for a bug where `$x:ident` followed by `where` // was pretty-printed as `$x:identwhere` (an invalid fragment specifier). macro_rules! outer { ($d:tt $($params:tt)*) => { #[macro_export] macro_rules! inner { ($($params)* where $d($rest:tt)*) => {}; } }; } #[macro_export] macro_rules! inner { ($x:ident where $ ($rest : tt)*) => {}; } fn main() {} ``` Notice the `$x:identwhere` in the before — an invalid fragment specifier that causes a hard parse error. The after correctly separates it as `$x:ident where`.

…volving-hrtb, r=jackh726 tests: Add regression test for async closures involving HRTBs I suspect the original code from rust-lang#59337 had several problems. The last problem fixed that made the code compile entered `nightly-2024-02-11`. The code fails to build with `nightly-2024-02-10`: $ rustc +nightly-2024-02-10 --edition 2018 tests/ui/async-await/async-closures/unifying-function-types-involving-hrtb.rs error[E0277]: expected a `FnOnce(&u8)` closure, found `{coroutine-closure@tests/ui/async-await/async-closures/unifying-function-types-involving-hrtb.rs:31:9: 31:30}` --> tests/ui/async-await/async-closures/unifying-function-types-involving-hrtb.rs:31:9 | 31 | foo(async move | f: &u8 | { *f }); | --- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected an `FnOnce(&u8)` closure, found `{coroutine-closure@tests/ui/async-await/async-closures/unifying-function-types-involving-hrtb.rs:31:9: 31:30}` | | | required by a bound introduced by this call | (Note that you must add `#![feature(async_closure)]` to test with such old nightlies, since they are from before stabilization of async closures.) So one of the following commits made the code build: <details> <summary>git log d44e3b9..6cc4843 --no-merges --oneline</summary> 4def373 manually bless an aarch64 test 04bc624 rebless after rebase 77f8c3c detect consts that reference extern statics 9c0623f validation: descend from consts into statics 4e77e36 unstably allow constants to refer to statics and read from immutable statics a2479a4 Remove unnecessary `min_specialization` after bootstrap 7b73e4f Allow restricted trait impls in macros with `min_specialization` e6f5af9 Remove unused fn fde695a Add a helpful suggestion d7263d7 Change wording 973bbfb No more associated type bounds in dyn trait cf1096e Remove unnecessary `#![feature(min_specialization)]` 3d4a9f5 Turn the "no saved object file in work product" ICE into a translatable fatal error bb60ded Loosen an assertion to account for stashed errors. 69a5264 Move some tests 4ef1790 tidy e59d9b1 Avoid a collection and iteration on empty passes 8b6b9c5 ast_lowering: Fix regression in `use ::{}` imports. 83f3bc4 Update jobserver-rs to 0.1.28 14e0dab Unify item relative path computation in one function f3c2483 Add regression test for non local items link generation f0d002b Correctly generate path for non-local items in source code pages c94bbb2 Clarify that atomic and regular integers can differ in alignment 7057188 make it recursive 7a63d3f Add tests for untested capabilities 548929d Don't unnecessarily lower associated type bounds to impl trait 22d582a For a rigid projection, recursively look at the self type's item bounds 540be28 sort suggestions for object diagnostic 9322882 Add a couple more tests 3bb384a Prefer AsyncFn* over Fn* for coroutine-closures aa6f45e Use `ensure` when the result of the query is not needed beyond its `Result`ness 8ff1994 Fix whitespace issues that tidy caught f0c6f5a Add documentation on `str::starts_with` 63cc3c7 test `llvm_out` behaviour 7fb4512 fix `llvm_out` to use the correct LLVM root b8c93f1 Coroutine closures implement regular Fn traits, when possible 08af64e Regular closures now built-in impls for AsyncFn* 0dd4078 Harmonize blanket implementations for AsyncFn* traits f3d32f2 Flatten confirmation logic 9a819ab static mut: allow reference to arbitrary types, not just slices and arrays </details> This was probably fixed by 3bb384a (rust-lang#120712). That PR does not have a big tests diff, so I assume the test we add does not exist elsewhere. It's hard to know for sure. Closes rust-lang#59337 since we add the test from that issue. In that issue there is a [proposal](rust-lang#59337 (comment)) for two minimized versions, but they both fail to compile with `nightly-2024-02-11`, so those reproducers are for different problem(s). ### Tracking Issue - rust-lang#62290

JonathanBrouwer · 2026-03-19T21:52:43Z

@bors r+ rollup=never p=5

rust-bors · 2026-03-19T21:52:46Z

📌 Commit 8b70af1 has been approved by JonathanBrouwer

It is now in the queue for this repository.

…uwer Rollup of 12 pull requests Successful merges: - #152909 (sess: `-Zbranch-protection` is a target modifier) - #153556 (`impl` restriction lowering) - #154048 (Don't emit rustdoc `missing_doc_code_examples` lint on impl items) - #153992 (bootstrap: Optionally print a backtrace if a command fails) - #154019 (two smaller feature cleanups) - #154059 (tests: Activate `must_not_suspend` test for `MutexGuard` dropped before `await`) - #154075 (Rewrite `query_ensure_result`.) - #154082 (Updates derive_where and removes workaround) - #154084 (Preserve braces around `self` in use tree pretty printing) - #154086 (Insert space after float literal ending with `.` in pretty printer) - #154087 (Fix whitespace after fragment specifiers in macro pretty printing) - #154109 (tests: Add regression test for async closures involving HRTBs)

rust-bors · 2026-03-20T04:12:24Z

💔 Test for f3d65af failed: CI. Failed job:

auto - dist-x86_64-msvc (web logs, enhanced plaintext logs)

Zalathar · 2026-03-20T04:32:18Z

No failure logs, so probably bogus.

Instead of retrying this rollup, I’ll make a new one to incorporate a few extra PRs.

rust-bors · 2026-03-20T06:06:40Z

This pull request was unapproved due to being closed.

davidtwco and others added 27 commits March 10, 2026 12:37

sess: -Zbranch-protection is a target modifier

cca2865

`-Zbranch-protection` only makes sense if the entire crate graph has the option set, otherwise the security properties that branch protection provides won't be effective. This flag is unstable so I don't think this warrants an MCP.

remove internal_impls_macro feature

aa7d812

move features into the correct section

e350a56

bootstrap: Optionally print a backtrace if a command fails

c8a2c46

Don't emit missing_doc_code_examples on impl items

74c51ce

Add more tests for rustdoc missing_doc_code_examples lint

6d3b780

Updates derive_where and removes workaround

bef4b47

Resolve paths for impl restrictions using smart_resolve_path

cec0a68

Add UI tests for path resolution errors of impl restrictions

4a60dae

Rollup merge of rust-lang#154019 - cyrgani:feature-clean, r=joboet

4ae63ed

two smaller feature cleanups Remove an unneeded feature gate for a private macro and sort the used features correctly by whether they are language or library features.

rust-bors bot added the rollup A PR which is a rollup label Mar 19, 2026

rustbot added A-run-make Area: port run-make Makefiles to rmake.rs A-tidy Area: The tidy tool labels Mar 19, 2026

rust-bors bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 19, 2026

This comment has been minimized.

Sign in to view

rust-bors bot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Mar 20, 2026

Zalathar mentioned this pull request Mar 20, 2026

Rollup of 15 pull requests #154123

Merged

JonathanBrouwer closed this Mar 20, 2026

rust-bors bot added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Mar 20, 2026

rustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Mar 20, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Rollup of 12 pull requests#154117

Rollup of 12 pull requests#154117
JonathanBrouwer wants to merge 27 commits intorust-lang:mainfrom
JonathanBrouwer:rollup-IfMXyaG

JonathanBrouwer commented Mar 19, 2026

Uh oh!

JonathanBrouwer commented Mar 19, 2026

Uh oh!

rust-bors bot commented Mar 19, 2026

Uh oh!

This comment has been minimized.

rust-bors bot commented Mar 20, 2026

Uh oh!

Zalathar commented Mar 20, 2026

Uh oh!

rust-bors bot commented Mar 20, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

12 participants

Uh oh!

Conversation

JonathanBrouwer commented Mar 19, 2026

Uh oh!

JonathanBrouwer commented Mar 19, 2026

Uh oh!

rust-bors bot commented Mar 19, 2026

Uh oh!

This comment has been minimized.

rust-bors bot commented Mar 20, 2026

Uh oh!

Zalathar commented Mar 20, 2026

Uh oh!

rust-bors bot commented Mar 20, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

12 participants