-
-
Notifications
You must be signed in to change notification settings - Fork 0
codegen wall 1: variable-string wasm backend ops (String.length / indexing / startsWith / fromCharCode) #560
Copy link
Copy link
Open
Labels
bindingsABI, FFI, WASM, and cross-language interop surfacesABI, FFI, WASM, and cross-language interop surfacesenhancementNew capability or improvement to existing behaviourNew capability or improvement to existing behaviourfeeds:valence-shellFeeds valence-shell's proofs/engineering (D127): judge progress by what it contributes thereFeeds valence-shell's proofs/engineering (D127): judge progress by what it contributes therepriority:p1High - schedule nextHigh - schedule nextscope:repoConfined to this repositoryConfined to this repositorystatus:readyFully specified and ready to be picked upFully specified and ready to be picked up
Description
Activity
Metadata
Metadata
Assignees
Labels
bindingsABI, FFI, WASM, and cross-language interop surfacesABI, FFI, WASM, and cross-language interop surfacesenhancementNew capability or improvement to existing behaviourNew capability or improvement to existing behaviourfeeds:valence-shellFeeds valence-shell's proofs/engineering (D127): judge progress by what it contributes thereFeeds valence-shell's proofs/engineering (D127): judge progress by what it contributes therepriority:p1High - schedule nextHigh - schedule nextscope:repoConfined to this repositoryConfined to this repositorystatus:readyFully specified and ready to be picked upFully specified and ready to be picked up
MIGRATION-PLAN.adoc:41-45,123-132,202-203: the [len:i32][utf8] layout exists (codegen.ml:375) but the ops are missing — variable-string operations cannot lower to the core-WASM backend. Gates all 71 STRING-GATED migration kernels (~12% of the 571-file corpus) and any real string-handling program on the reference backend. Doc-stated, previously issue-untracked. v1-blocking for a 'language base components' claim on the blessed backend. Part of the v1-readiness ledger.