§18A.12 — true iff a wasm module is PRELOADED (RESOLVED, not merely
in-flight) for bridge (or, when omitted, the most-recently-resolved
bridge). Synchronous — reads the resolved slot, never awaits. The exact
predicate createCauslWasmSync uses to decide whether to throw
CauslWasmNotPreloadedError.
It is NOT "a construct right now would return a graph." A host on which
the WasmGC engine cannot COMPILE resolves a capability-unavailable SENTINEL
into the preload slot — deliberately, so the failure lands at the construct
site naming the host rather than at app init — and the sentinel reads as
preloaded here. causl/causl-wasm-ts#363, measured with
__forceWasmCompileUnavailableForTests armed:
So gating a boot on this predicate does not remove the try / catch — it
answers "has a preload resolved for this bridge", which is exactly true on
that host, and the only readiness test that is a prediction is constructing
a graph and seeing. The @internal twin isWasmSyncEngineReady()
(src/wasm-registry.ts) carries the same caveat; this is the half an
adopter can reach.
§18A.12 —
trueiff a wasm module is PRELOADED (RESOLVED, not merely in-flight) forbridge(or, when omitted, the most-recently-resolved bridge). Synchronous — reads the resolved slot, never awaits. The exact predicate createCauslWasmSync uses to decide whether to throw CauslWasmNotPreloadedError.It is NOT "a construct right now would return a graph." A host on which the WasmGC engine cannot COMPILE resolves a capability-unavailable SENTINEL into the preload slot — deliberately, so the failure lands at the construct site naming the host rather than at app init — and the sentinel reads as preloaded here. causl/causl-wasm-ts#363, measured with
__forceWasmCompileUnavailableForTestsarmed:await preloadCauslWasm({ bridge: 'wasmgc-classic' }) -> RESOLVED isCauslWasmPreloaded() -> true createCausl() -> THROWS CAUSL_WASM_ENGINE_UNAVAILABLE
So gating a boot on this predicate does not remove the
try/catch— it answers "has a preload resolved for this bridge", which is exactly true on that host, and the only readiness test that is a prediction is constructing a graph and seeing. The@internaltwinisWasmSyncEngineReady()(src/wasm-registry.ts) carries the same caveat; this is the half an adopter can reach.