GeezerVison

Reviewing files that changed from the base of the PR and between 563dc0f and b156296.

• crates/compiler-core/src/bytecode.rs (3 hunks)
• crates/jit/src/instructions.rs (2 hunks)
• crates/vm/src/frame.rs (5 hunks)

• GitHub Check: Run snippets and cpython tests (windows-latest)

crates/jit/src/instructions.rs (4)

556-559: PopBlock instruction is stubbed with TODO.

Similar to Resume, PopBlock needs proper block management implementation for complete JIT support.

---

439-443: BuildTuple implementation looks correct.

The tuple building correctly pops elements from the stack and creates a JitValue::Tuple.

---

464-517: CompareOperation implementation handles int/bool/float comparisons correctly.

The implementation properly extends bools to i64 for comparison and uses appropriate integer/float comparison conditions.

---

641-655: UnpackSequence correctly validates tuple size.

The implementation appropriately checks that the tuple size matches the expected size before unpacking, and reverses the elements before extending the stack to maintain proper order.

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

534-558: BeforeAsyncWith implementation looks correct.

The async context manager protocol is properly implemented: retrieves __aenter__, invokes it, then gets __aexit__ and pushes both onto the stack in the correct order.

---

1106-1225: MatchClass implementation is comprehensive.

The pattern matching for class patterns correctly handles:

• Instance checking
• __match_args__ extraction for positional arguments
• MATCH_SELF behavior for built-in types
• Keyword attribute extraction
• Proper error handling for missing attributes

---

1227-1294: MatchKeys implementation correctly uses .get() method pattern.

The implementation properly follows CPython's approach using map.get(key, dummy) for atomic key checking, which handles collections.defaultdict and similar types correctly without triggering __missing__.

---

1067-1081: LoadMethod pushes three values: target, is_method flag, and func.

This correctly implements the method loading pattern where:

1. target is the object for bound methods (or None for attributes)
2. is_method boolean distinguishes bound methods from plain attributes
3. func is the actual callable

The corresponding execute_method_call at lines 1876-1896 correctly handles both cases.

---

808-819: EndAsyncFor correctly handles StopAsyncIteration.

The implementation properly:

1. Pops the exception
2. Pops the except handler block
3. Validates block level matches stack size
4. Pops the async iterator
5. Checks for StopAsyncIteration and clears the exception stack

---

1460-1476: SWAP instruction implementation is correct.

The implementation correctly matches CPython 3.11+ semantics. For SWAP(n), the code calculates j = len - index_val, which swaps TOS (at index len - 1) with the element at distance n below it (at index len - n). This implements the specified semantics where STACK[-n] and STACK[-1] are exchanged.

crates/compiler-core/src/bytecode.rs (6)

551-800: Instruction enum is alphabetically sorted.

The enum variants from BeforeAsyncWith through YieldValue appear to be properly sorted alphabetically, fulfilling the PR objective.

---

803-805: LAST_INSTRUCTION correctly updated to YieldValue.

Since YieldValue is the last variant alphabetically, this constant is correctly set for marshaling bounds checking.

---

618-620: ContainsOp uses tuple-style variant as intended.

The conversion from named struct-style (ContainsOp { invert: Arg<Invert> }) to tuple-style (ContainsOp(Arg<Invert>)) aligns with the PR objectives for simplifying enum variants.

---

1550-1569: label_arg correctly includes all jump instructions.

All instructions that contain Label arguments are properly listed in this match, including the newly added Break and Continue variants.

---

1800-1907: fmt_dis match arms are alphabetically sorted.

The display formatting match arms are properly sorted to match the instruction enum ordering, maintaining consistency throughout the codebase.

---

1674-1676: SetupAnnotation, SetupLoop, SetupFinally, EnterFinally, EndFinally all have stack effect 0.

These control flow setup instructions correctly report zero stack effect as they manage block state rather than stack values.