On Fri, Jul 10, 2026 at 4:26 PM Alice Ryhl <[email protected]> wrote: > > I understand this is probably due to a new function in Rust stdlib that > is no_return, so probably not caused by this patch even if this is > triggering it.
I can take a look and perhaps push a patch via `rust-fixes`, which would make it fixed by the time this one lands in the merge window. Cheers, Miguel
