From 39a9001f54e011d200384c3386d3d587ebcd4a99 Mon Sep 17 00:00:00 2001 From: bQUARKz Date: Wed, 18 Feb 2026 16:05:44 +0000 Subject: [PATCH] pr2.5 --- files/TODOs.md | 51 -------------------------------------------------- 1 file changed, 51 deletions(-) diff --git a/files/TODOs.md b/files/TODOs.md index cda5489a..3ba101cf 100644 --- a/files/TODOs.md +++ b/files/TODOs.md @@ -1,54 +1,3 @@ -# PR-2.5 — Prepare Call Frame Structure for Closures and Coroutines - -### Briefing - -Before introducing closures and coroutines, the call frame structure must be neutral and future-proof, without HIP-specific fields. - -### Target - -* Simplify the call frame to a minimal, generic structure. -* Remove any HIP/borrow/gate-related fields. - -### Work items - -* Review the call frame struct. -* Remove fields tied to scope frames, borrow state, or gates. -* Ensure the frame contains only: - - * Function identifier. - * Program counter. - * Base stack pointer. - * Locals or register area (if applicable). -* Keep the structure simple and extensible. - -### Acceptance checklist - -* [ ] Call frame struct has no HIP-related fields. -* [ ] VM call/return paths compile and work. -* [ ] `cargo test` passes. - -### Tests - -* Existing call-related tests must still pass. - -### Junie instructions - -**You MAY:** - -* Remove unused fields from the frame. -* Refactor call/return code to match the new structure. - -**You MUST NOT:** - -* Introduce closure or coroutine logic yet. -* Redesign the call stack architecture. - -**If unclear:** - -* Ask before changing frame responsibilities. - ---- - # PR-2.6 — Remove Dead Runtime Modules and Symbols ### Briefing