Gap capture: an optional call's short-circuit record can pair with another evaluation (four cases)

Offen
#162 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
javascript
Bereich
testing-qa

Rechercherichtung

Start with pr147-review.md at “Delta round 2”, D1, then read the gap oracle’s Limits and the simulations in /tmp/rev147-scripts/q2.mjs and q3.mjs. The issue describes four record pairing failures and states that fixing them may require a statement level rewrite or another design. Done means choosing and implementing a design that prevents those failures; no tests or source files are named.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

#147 makes an optional call f?.() pass its short-circuit on to the next ?. link of its chain:

  • the link's receiver opens a record (open);
  • the call's empty argument spread marks the newest open record as run (ran), and it runs only when the call does;
  • the link reads the newest record and closes it (chain).

The records of one call site form a stack, so a record pairs with its evaluation only where evaluations of the same expression nest and each one ends. The oracles repo has no coverage map, so this issue records the four cases that break the pairing. Each needs an owner. No history of the gap oracle generates any of them, and the gap oracle's Limits state them.

# Case Record left behind Consequence for the next ?. link
1 An evaluation of the same expression nested in the receiver, which throws after its call ran, and the throw is caught there run, left open With the outer method absent: a false infection, and a false throw under the link's mutant (P3)
2 The same nesting in the method lookup run, left open The same: a false throw (P3)
3 An evaluation nested in the call's arguments or the method's body, which throws before its own call runs, and the throw is caught there not run, left open With the outer call having run and returned nothing: a false skip, so the mutant is judged without a run as not-distinguished. This is the class of #109 (P5)
4 Two async evaluations of the same expression interleaved at an await ((await r(a))?.f?.(await g())?.v) the evaluations close each other's records a false skip or a false throw

The review that found them is pr147-review.md, "Delta round 2", D1. The simulations are in /tmp/rev147-scripts/q2.mjs and q3.mjs.

A pairing per evaluation would need a binding that an expression rewrite cannot create without changing this, await or arguments. For example, an arrow wrapper breaks await and yield. A fix would need a statement-level rewrite or another design.

The numeric path for nested ?. links (shortCircuited) is not affected. Nothing runs between a link that short-circuits and its consumer.

Filed under v21.2 P11 and G36, as a stated limit with an owner.

This issue was written by Isaac.

Vorherrschende Sprache
JavaScript
Sterne
5
Forks
1
Ø Merge
11 Std. 18 Min.
Gemergte PRs (30 T.)
66

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus TanStack/oracles

Alle Issues in TanStack/oracles

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.