Skip to content

🔧 chore(vm): record stack frame's origin - #248

Open
SimonShiki wants to merge 1 commit into
feat/ts-vm-2from
fix/140
Open

🔧 chore(vm): record stack frame's origin#248
SimonShiki wants to merge 1 commit into
feat/ts-vm-2from
fix/140

Conversation

@SimonShiki

Copy link
Copy Markdown
Member

Description

Record stack frame's block container source, in order to fix #140.

Proposed Changes

  1. For every stack frame, they have a new blockContainer field that records where the stack frame's executing block from.
  2. Unless explictly specified by pushStack, the descendant stack frame will inherit from its parent.
  3. the procedures_call that calls stepToProcedure() will declare its block container context.

Test Coverage

Added #140 related tests.

Additional Context

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Aug 11, 2026

Copy link
Copy Markdown

Deploying clipcc-preview with  Cloudflare Pages  Cloudflare Pages

Latest commit: fb43b37
Status: ✅  Deploy successful!
Preview URL: https://a3fa174d.clipcc-preview.pages.dev
Branch Preview URL: https://fix-140.clipcc-preview.pages.dev

View logs

@SimonShiki
SimonShiki requested a review from alexcui03 August 11, 2026 10:02
@SimonShiki SimonShiki added the bug Something isn't working label Aug 11, 2026
@SimonShiki SimonShiki self-assigned this Aug 11, 2026
Signed-off-by: SimonShiki <sinangentoo@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant