@WG-prioritization/alerts issue #77458 has been requested for prioritization.
I-nominated
?P-low IMO, the only people that could run into this are contributors trying to debug things
you could make an argument this makes it harder to get started in the codebase, but no more so than rustdoc having random ICEs if you call tcx.whatever()
on a fake DefId
I requested prioritization because it seems there might be something weird going on that could affect other things
It's not necessarily limited to rustc_middle::ty::Ty
, that's just where it was found, correct?
well in the sense that you can print debug output anywhere, yes
but debug output is never user-facing
the absolute worst that can happen is that this panics while panicking and aborts
but that just turns an ICE -> abort
I'm saying that this could happen on any type, it's just that Ty
is the one that triggers this. Is that not true?
So IIUC it's not an issue specific to Ty
, it's just where the bug was found
any type that has a DefPath
, yes
I think we're miscommunicating :smile:
Is this issue because of how Debug
is implemented for Ty
?
(Or some field of Ty
?)
it's because of how Debug
is implemented for DefPath
, which is one of the fields on Ty
Ah. Let me go look at that PR again
Hmm, but DefPath
uses #[derive(Debug)]
...
sorry, this isn't actually Debug
, it's print_def_path
: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/ty/print/struct.FmtPrinter.html#method.print_def_path
(it says in the backtrace)
Hmm, still don't see what's causing this
But I guess if it's just for Ty
, then P-low
probably sounds good
I'll assign a P-low
, but open to further reasoning on this
Issue #77458's prioritization request has been removed.