Skip to content

Bugs/typos found by AI#161

Open
KristofferC wants to merge 10 commits into
masterfrom
kc/ai_bugs
Open

Bugs/typos found by AI#161
KristofferC wants to merge 10 commits into
masterfrom
kc/ai_bugs

Conversation

@KristofferC

Copy link
Copy Markdown
Member

These were found by Claude/ChatGPT and I do not think it is all AI slop. But I am a bit too much out of the loop of this package to feel confident merging it myself. I did add Revise as a downstream test, though.

  • codeedges: fix undefined variable pcexec in get_return
  • codeedges: fix loop control flow in add_typedefs!
  • add Revise as a downstream test
  • codeedges: include default constructors in typedef slices
  • codeedges: reset state when reusing slice controllers
  • codeedges: return values from the current selective run
  • signatures: handle forward declarations and operator names
  • docs: correct API examples and descriptions
  • docs: refresh the documentation environment
  • cleanup: remove unused dominator tree implementation

KristofferC and others added 10 commits July 19, 2026 21:41
The JuliaInterpreter 0.10 update (bcb6f63) restructured `selective_eval!`
into `SelectiveInterpreter` but left a reference to the old local variable
`pcexec` in `JuliaInterpreter.get_return`. Any call that stopped at a
non-`return` statement whose ssavalue was assigned (e.g. reusing a frame,
as the documentation demonstrates, with a controller that has termination
points) threw `UndefVarError: pcexec` instead of returning the stored value.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The `continue` after processing a typedef block sat inside the inner
`for` loop over typedef blocks, so it never restarted the outer `while`
loop as intended. Two consequences:

- After advancing `idx` past the matched block, the inner loop kept
  matching the *new* `idx` against the remaining blocks. When two type
  definitions are adjacent in the lowered code (e.g. two consecutive
  `abstract type`s on Julia ≤1.11), requiring any statement of the first
  block marked the entire second block as required, causing unrelated
  type definitions to be (re)evaluated.
- Falling out of the inner loop, the trailing `idx += 1` skipped the
  statement immediately after the block from ever being examined.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@KristofferC
KristofferC requested review from aviatesk and timholy July 19, 2026 21:07
@KristofferC KristofferC changed the title Bus/typos found by AI Bugs/typos found by AI Jul 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant