Skip to content

guide: a write waits for an action when a displayed equation reads its source together with a source the action holds, from onFlush too #77

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.

The guide shipped in @reactivescript/compiler 0.3.1. Run as: 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-shown.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>
    <p>both.open: {both.open ? "yes" : "no"}</p>
  </div>
}
step screen
mount open: yes, page: 1, both.open: yes
click go open: yes, page: 1, both.open: yes
click close open: yes, page: 1, both.open: yes
100 ms later open: yes, page: 1, both.open: yes
the wait resolves open: no, page: 2, both.open: no

The first paragraph reads open alone and waits with the third. The action never writes open. With the close
button removed and onFlush(() => { open := false }) added after page := 2 in go, the screen is the same at
every step: the onFlush write waits too.

This is H-3 (both is derived from the held page, and its reader joins), and S-solid-4's sum variant is the
nearest scenario, there with a flight in place of an action's write.

The guide gives two cases and two remedies, and b-shown.rx is neither case and gets no help from either remedy:

  • guide/async.md §4: "A click waits for an action it has nothing to do with. A plain write to a source an
    action in flight has written or guessed joins that action's hold (H-2): a click that clears the action's error
    waits for the server. Keep such a write off the action's sources, or make it an onFlush run."
  • guide/async.md §3, the table: "Land a UI write now and keep it (close a menu, clear a message) |
    onFlush(() => { x := v }) (EF-8)".
  • guide/reference.md, "Actions": "onFlush(() => { … }): runs right after this run's instant, even while the
    action holds it. Use it for a write that must land now, such as clearing an input or an error (EF-8)."

One view expression over the same two values does not join. With the both line and its paragraph replaced by
<p>{(open ? "open" : "closed") + " on " + page}</p>, the click on close shows open: no and closed on 1. That
fits H-3, which serves "a reader of a source written by another open change" and says "An equation never
serves". It does not fit EF-8's parenthesis, "(H-2, D-8; a write to a held slot, or a reader of
both)", read literally: this is a reader of both and its write commits alone. V-1 and E-2 also make {e} a reader
"with equation e", so nothing in the guide or the spec's surface rules tells an author that giving the
expression a name changes when the write lands.

Suggested sentence, in "What lands together, and what waits" or in §4 after "or make it an onFlush run": a write
also waits when an equation the view reads depends on its source and on a source the action holds, from an
onFlush run too; one view expression that reads both does not wait.

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