Fix WASM reactive signals: unify context/scope, fix flush-subscribers

Browse Source

Three root causes for reactive attribute updates not propagating in WASM:

1. `context` CEK special form only searched kont provide frames, missing
   `scope-push!` entries in the native scope_stacks hashtable. Unified by
   adding scope_stacks fallback to step_sf_context.

2. `flush-subscribers` used bare `(sub)` call which failed to invoke
   complex closures in for-each HO callbacks. Changed to `(cek-call sub nil)`.

3. Test eagerly evaluated `(deref s)` before render-to-dom saw it.
   Fixed tests to use quoted expressions matching real browser boot.

WASM native: 10/10, WASM shell: 26/26.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

...

This commit is contained in:

giles

2026-03-31 15:12:25 +00:00

parent e1770499df

commit 521782d579

9 changed files with 563 additions and 10 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

BIN

shared/static/wasm/sx_browser.bc.wasm.assets/sx-a0c22109.wasm Normal file

Binary file not shown.

1

shared/static/wasm/sx_browser.bc.wasm.assets/sx-a0c22109.wasm.map Normal file

File diff suppressed because one or more lines are too long