Add issue number to novel violation warning

diff --git a/src/librustc_mir_build/hair/pattern/const_to_pat.rs b/src/librustc_mir_build/hair/pattern/const_to_pat.rs
index 8c4230dfa5d6d72546d4bc47908293778707ced1..1aed8e844b60b02f261b2b3e27fddbe7be608ae2 100644 (file)
--- a/src/librustc_mir_build/hair/pattern/const_to_pat.rs
+++ b/src/librustc_mir_build/hair/pattern/const_to_pat.rs
@@ -109,9 +109,12 @@ fn to_pat(
 
             // 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;
             }