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

Aberta
#162 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
javascript
Domínio
testing-qa

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

#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.

Linguagem predominante
JavaScript
Estrelas
5
Forks
1
Merge médio
11h 18min
PRs com merge (30d)
66

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TanStack/oracles

Todas as issues de TanStack/oracles

Issues semelhantes

Mais issues de JavaScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.