Pin openscad_cpp_evaluator 0.26.1: step-into-child works from children() - #202
Merged
Conversation
0.26.1 aims step-into-child at the children a children() call forwards. Stepping to a child from inside a module's own children() previously found no target and degraded into a continue, running the script to completion and ending the session. Verified against the published wheel for both child kinds: from children(), the step now lands on a forwarded cube() and on a forwarded user module alike. The built-in was a red herring in the original report -- where the pause was is what mattered. The run-off-the-end message stays as the honest answer for whatever else reaches no child, with its comment corrected: it previously said the cause was not understood. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Picks up openscad_cpp_evaluator#83.
Stepping to a child from inside a module's own
children();found no target and degraded into acontinue— running the script to completion and ending the debug session.childStatementPositionsreturned a node's own children, and achildren()call has none; it forwards the enclosing invocation's, which live on the context.Verified against the published wheel, both child kinds:
The built-in was a red herring in the original report — a user module failed identically. Where the pause was is what mattered.
Also
The run-off-the-end message stays as the honest answer for whatever else reaches no child, but its comment is corrected: it previously said the cause was not understood, and now it is.
Verification
Editable install removed,
uv lock --refresh-package+uv syncpulled 0.26.1 from PyPI (all six files confirmed present first), andopenscad_cpp_evaluator.__file__verified in site-packages.653 Python tests and all six GUI verifiers pass.
🤖 Generated with Claude Code