GeezerVison

crates/codegen/src/compile.rs (1)

1384-1394: Rename to Instruction::Copy is safe and complete; update stale documentation in frame.rs.

The rename from CopyItem to Instruction::Copy is consistently applied across all 35+ call sites in compile.rs. The variant correctly maps to CPython's COPY opcode (opcode 61) and the stack effect is properly calculated. However, stale references remain in crates/vm/src/frame.rs at lines 766, 767, 772, and 775—these are comments and error messages that still mention CopyItem and should be updated to use Copy for consistency:

• Lines 766–767: Comments explaining Copy semantics
• Line 772: Error message "CopyItem ERROR: ..."
• Line 775: Panic message "CopyItem: stack underflow"

The underlying code at line 765 is correct and handles the instruction properly.

crates/vm/src/frame.rs (1)

765-780: Stale comments reference old instruction name.

The comments on lines 766-768 and 772 still reference CopyItem, but the instruction has been renamed to Copy. Update the comments for consistency.

📝 Suggested fix

             bytecode::Instruction::Copy { index } => {
-                // CopyItem { index: 1 } copies TOS
-                // CopyItem { index: 2 } copies second from top
+                // Copy { index: 1 } copies TOS
+                // Copy { index: 2 } copies second from top
                 // This is 1-indexed to match CPython
                 let idx = index.get(arg) as usize;
                 let stack_len = self.state.stack.len();
                 if stack_len < idx {
-                    eprintln!("CopyItem ERROR: stack_len={}, idx={}", stack_len, idx);
+                    eprintln!("Copy ERROR: stack_len={}, idx={}", stack_len, idx);
                     eprintln!("  code: {}", self.code.obj_name);
                     eprintln!("  lasti: {}", self.lasti());
-                    panic!("CopyItem: stack underflow");
+                    panic!("Copy: stack underflow");
                 }