MIRROR: javascript for 🐜's, a tiny runtime with big ambitions
update tech-debt.md
+14
+14
docs/exec-plans/tech-debt.md
+14
docs/exec-plans/tech-debt.md
···
15
15
- Proposed fix:
16
16
- Owner:
17
17
- Status:
18
+
19
+
## Open Items
20
+
21
+
- Area: `src/modules/readline.c`
22
+
- Issue: Rendering assumes readline owns the full visible prompt line, so redraws are anchored to the logical prompt text instead of the terminal position where editing actually begins.
23
+
- Impact: Full redraw paths can clobber externally rendered prefixes, boxed prompts, or other same-line UI written before `question()` or `prompt()` starts editing.
24
+
- Proposed fix: Track an explicit render origin / prompt anchor, separate logical prompt text from the screen position where input begins, and make redraws preserve external prefixes and custom prompt chrome.
25
+
- Status: open
26
+
27
+
- Area: Silver compiler
28
+
- Issue: `sv_compiler_t` scratch storage is still allocated per compilation, so repeated compiles in a long-lived process pay allocator churn for locals, bytecode buffers, constants, atoms, upvalue descriptors, loops, srcpos data, and maybe slot-type scratch.
29
+
- Impact: One-shot CLI compiles are fine, but a REPL, watch mode, embedder, or other long-lived process cannot yet recycle compiler scratch space across compiles.
30
+
- Proposed fix: Add a real `compile_pool` scratch allocator after the `compile_ctx` extraction. Pool the resizable arrays for `locals`, `local_lookup_heads`, `code`, `constants`, `atoms`, `upval_descs`, `loops`, `srcpos`, and potentially `slot_types`. Keep `line_table` separate or make it poolable scratch, since it is derived from the current source buffer rather than a semantic cache.
31
+
- Status: backlog