León Orell Valerian Liehr

I am not sure what the issue is. The message and the span of the diagnostic both look correct to me. It's true that `returns_true` is not defined inside of...

Ah, thanks for your reply. That cleared things up for me :) So given the following minimized reproducer: ```rust mod one { pub trait Tr { fn meth(); } }...

Further, we could probably also improve the diagnostic for the case when the trait *isn't* imported: ```rust mod one { pub trait Tr { fn meth(); } } mod two...

@rustbot label -E-needs-mcve

> Interesting, so `const` blocks behave differently from normal blocks and `unsafe` blocks ... I see what you mean (replacing `const` with an empty string or with `unsafe` leads to...

> Though these errors aren't parsing errors in rustc I beg to differ: ```rust #[cfg(FALSE)] fn f () { match () { () => { [0] }[..], } } ```...

Okay, so should I ask T-lang on Zulip or would you like to do the favor? Either one is fine for me. Edit: [Zulip stream](https://rust-lang.zulipchat.com/#narrow/stream/213817-t-lang/topic/const.20blocks.20differ.20from.20normal.20and.20from.20unsafe.20blocks).

The discussion didn't lead to anything we could immediately act on. scottmcm added this issue to the list of unresolved questions on the tracking issue for inline consts (rust-lang/rust#76001). Seems...

Can it handle `"${ "${ 0 }" }"` (nested interpolated strings)?

Okay, I've simplified my PR to make it easier to review. Once again, it's an error to impl `!Copy` for types like `&mut Local`, `dyn Local` and other non-ADTs.