Add issue number to novel violation warning
This commit is contained in:
parent
38e921b2c1
commit
3a1207f688
|
@ -109,9 +109,12 @@ impl<'a, 'tcx> ConstToPat<'a, 'tcx> {
|
|||
|
||||
// This can occur because const qualification treats all associated constants as
|
||||
// opaque, whereas `search_for_structural_match_violation` tries to monomorphize them
|
||||
// before it runs. See #73431 for an example.
|
||||
// before it runs.
|
||||
//
|
||||
// FIXME(#73448): Find a way to bring const qualification into parity with
|
||||
// `search_for_structural_match_violation`.
|
||||
if structural.is_none() && mir_structural_match_violation {
|
||||
warn!("MIR const-checker found novel structural match violation");
|
||||
warn!("MIR const-checker found novel structural match violation. See #73448.");
|
||||
return inlined_const_as_pat;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue