Skip to content

An unread equation over two sources makes a write to one wait for an action that holds the other (E-3 against CP-4b's createMemo) #76

Open

Description

@cgaaf

Found while building a component library on ReactiveScript. Written with Claude Fable 5.2 (in Claude Code), which also ran the reproductions; all of them were rerun before posting.

@reactivescript/compiler 0.3.1 through @solidjs/vite-plugin 3.0.0-next.57 on a Vite dev server, mounted with
const app = createApp({ root }); app.mount(main(app)) from @reactivescript/runtime 0.3.1, in Chromium, on
solid-js 2.0.0-rc.22 and on 2.0.0. A Playwright script clicks the buttons and reads the text of the <p>
elements.

api.js:

export const wait = (ms, value) => new Promise((resolve) => setTimeout(() => resolve(value), ms));

b.rx:

import { wait } from "./api.js"

export default component App() {
  source open := true
  source page := 1
  both = { open: open, page: page }
  action go() {
    page := 2
    try { await wait(300, 0) } catch (e) { }
  }
  <div>
    <button onClick={() => { go() }}>go</button>
    <button onClick={() => { open := false }}>close</button>
    <p>open: {open ? "yes" : "no"}</p>
    <p>page: {page}</p>
  </div>
}
step b.rx b.rx without the both line
mount open: yes, page: 1 open: yes, page: 1
click go open: yes, page: 1 open: yes, page: 1
click close open: yes, page: 1 open: no, page: 1
100 ms later open: yes, page: 1 open: no, page: 1
the wait resolves open: no, page: 2 open: no, page: 2

Expected: the right-hand column for both. Nothing reaches both: no reader, no effect, no other equation.

  • E-3 (spec/02-core.md): "An equation's body is evaluated only when a reader, an effect's compute half, or
    another demanded equation reaches it in the current instant. Unreached equations have no observable cost or
    effect."
  • V-4 (spec/00-vocabulary.md): "An equation counts only through the readers that reach it; an effect, a
    snapshot read (V-11), or an unread equation is never a reader."
  • H-3 (spec/05-holds.md) makes a join a reader's: "a reader that consumes a value derived from c's held
    writes, or a landed answer of c, joins c".
  • guide/language.md, "Declarations": "Equations are lazy and exact".

The compiler does what CP-4b (spec/11-compiler.md) pins: memo(name, fn, opts) lowers "an equation (E-1)" over
createMemo, and the runtime's memo is createMemo(named(name, fn), opts2). That memo is eager, so the conflict
is between E-3 and CP-4b. ref/compile/rt.ts has the same createMemo call; I did not run ref/.

The page below is the same program on solid-js alone, with the same clicks. As written it gives the left-hand
column. With ?lazy in the URL it gives the right-hand column.

<!doctype html> <button>go</button><button>close</button>
<p></p>
<p></p>
<script type="module">
  import { createRoot, createSignal, createMemo, createRenderEffect, action } from "solid-js";
  const lazy = new URLSearchParams(location.search).has("lazy");
  const [go, close] = document.querySelectorAll("button");
  const [openText, pageText] = document.querySelectorAll("p");
  createRoot(() => {
    const [open, setOpen] = createSignal(true);
    const [page, setPage] = createSignal(1);
    createMemo(() => ({ open: open(), page: page() }), lazy ? { lazy: true } : undefined); // never read
    const run = action(function* () {
      setPage(2);
      yield new Promise((r) => setTimeout(r, 300));
    });
    go.onclick = () => run();
    close.onclick = () => setOpen(false);
    createRenderEffect(open, (v) => {
      openText.textContent = "open: " + (v ? "yes" : "no");
    });
    createRenderEffect(page, (v) => {
      pageText.textContent = "page: " + v;
    });
  });
</script>

(Served by the same Vite server, which resolves the solid-js import.)

Not tested: what else changes if an equation is emitted with { lazy: true }. Solid's cheatsheet says a lazy memo
will "autodispose when unobserved", and spec/02-core.md already records one lazy-memo divergence, for pre.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions