[Lldb-commits] [clang] [lldb] [UBSan][BoundsSafety] Implement support for more expressive "trap reasons" (PR #154618)

[via lldb-commits]

================
@@ -30,6 +30,7 @@ def CLASS_REMARK    : DiagClass;
 def CLASS_WARNING   : DiagClass;
 def CLASS_EXTENSION : DiagClass;
 def CLASS_ERROR     : DiagClass;
+def CLASS_TRAP      : DiagClass;
----------------
Sirraide wrote:

Hmm, I wonder if we really need a new diagnostic class for this; my only concern is that some code paths in the diagnostics formatter etc. might not like it if you hand them a new diag class—that said, that is definitely a way to make sure we don’t accidentally issue these diagnostics, in which case we should probably put an assertion in `DiagnosticsEngine::Report(Level DiagLevel, const Diagnostic &Info)`.

https://github.com/llvm/llvm-project/pull/154618