Problem
The Deno source-to-source backend can consume a Thenable-returning extern because the emitted JS consumer can await it directly. The wasm/Node backend (--vscode-extension → codegen_node.ml + packages/affine-vscode/mod.js) cannot: there is no await/thenable-resolution mechanism for a wasm guest — no ExprAwait, no AWAIT token, and the issue-#103 design sketch's thenableThen / thenableResultString/Int/Json primitives were explicitly deferred in slice-1 and never built.
A mod.js comment (added in #200) says the wasm path "needs the thenable-resolution primitives — tracked in #199", but #199 became the host→guest callback ABI (function-value handlers), which is a different axis (host calls guest). Consuming a host Thenable result in a wasm guest is still untracked and unbuilt. This issue is that tracking item.
Impact
languageClientSendRequest (#200) returns a Thenable handle the wasm guest cannot resolve. So the rsr-certifier vscode pilot (PR-5d, #103 acceptance) can restore the withProgress-wrapped UX (host→guest callback works) but not the live in-process data (status-bar tier/score, DiagnosticCollection population, dynamic webview) which require reading the rsr/getCompliance (server: rsr.checkCompliance executeCommand, {tier,tier_code,score}) result.
Design space (not decided)
Acceptance
Refs #103, #199
Problem
The Deno source-to-source backend can consume a
Thenable-returning extern because the emitted JS consumer canawaitit directly. The wasm/Node backend (--vscode-extension→codegen_node.ml+packages/affine-vscode/mod.js) cannot: there is noawait/thenable-resolution mechanism for a wasm guest — noExprAwait, no AWAIT token, and the issue-#103 design sketch'sthenableThen/thenableResultString/Int/Jsonprimitives were explicitly deferred in slice-1 and never built.A
mod.jscomment (added in #200) says the wasm path "needs the thenable-resolution primitives — tracked in #199", but #199 became the host→guest callback ABI (function-value handlers), which is a different axis (host calls guest). Consuming a hostThenableresult in a wasm guest is still untracked and unbuilt. This issue is that tracking item.Impact
languageClientSendRequest(#200) returns aThenablehandle the wasm guest cannot resolve. So the rsr-certifier vscode pilot (PR-5d, #103 acceptance) can restore thewithProgress-wrapped UX (host→guest callback works) but not the live in-process data (status-bar tier/score,DiagnosticCollectionpopulation, dynamic webview) which require reading thersr/getCompliance(server:rsr.checkComplianceexecuteCommand,{tier,tier_code,score}) result.Design space (not decided)
thenableThen(t, handlerClosure)(now expressible via the Deno source-to-source host→guest callback ABI (blocks withProgress/registerCommand/onDidSave) #199 function-value ABI) +thenableResultJson(t)settle-readers; the host re-enters the guest closure when the Thenable settles.async fn/awaitwith codegen emitting awaited JS shims (the Async-extern ABI: bind withProgress + LanguageClient.sendRequest #103 "much bigger lift").Acceptance
Thenable(languageClientSendRequest).rsr/getComplianceand populates status-bar/diagnostics/webview from the live result.Refs #103, #199