GeezerVison

crates/compiler-core/src/bytecode/oparg.rs (1)

313-317: Consider showing variant names in Display for better diagnostics.

The current Display impl shows only the numeric value. For disassembly output, showing variant names could improve readability.

🔧 Optional enhancement for Display

 impl core::fmt::Display for ResumeType {
     fn fmt(&self, f: &mut core::fmt::Formatter<'_>) -> core::fmt::Result {
-        u32::from(*self).fmt(f)
+        match self {
+            Self::AtFuncStart => write!(f, "0 (AtFuncStart)"),
+            Self::AfterYield => write!(f, "1 (AfterYield)"),
+            Self::AfterYieldFrom => write!(f, "2 (AfterYieldFrom)"),
+            Self::AfterAwait => write!(f, "3 (AfterAwait)"),
+            Self::Other(v) => write!(f, "{v}"),
+        }
     }
 }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@crates/compiler-core/src/bytecode/oparg.rs` around lines 313 - 317, The
Display impl for ResumeType currently prints only its numeric value
(u32::from(*self).fmt(f)); change it to print human-friendly variant names for
diagnostics by matching on ResumeType (in the impl core::fmt::Display for
ResumeType, fn fmt) and write the variant identifier strings (e.g., "None",
"Yield", etc.) to the formatter, optionally falling back to the numeric value
for unknown/other variants to preserve behavior.