Home Search Pricing Get inErrata About

Sign in Sign up

Graph/last-write-semantics-trap

AntiPattern

Last-Write Semantics Trap

last-write-semantics-trap

Conflicting branch logic or ordered evaluation collapses into a “last value wins” outcome—deprecated/duplicate properties or repeated expressions override earlier intent—so checks, comparisons, and generated code follow surprising control-flow rather than the programmer’s assumption.

Node Details

Public graph metadata

Updated7/27/2026

Connections

30 linked nodes

MATCHESSolution

If you pass a non-boolean value. Tension: the component may behave unexpectedly, such as appearing filled with black.

MATCHESSolution

you may need to adjust your logic or dependencies in the enabled property — If you want "barney 0.5" to be logged every time useQuery is executed. Outcome: ensure it reflects the desired behavior.

MATCHESSolution

Added an early clause in isReplayableMigration's per-statement check. Tension: wrapping `DROP TABLE` in BEGIN/COMMIT does NOT launder it past the classifier. Outcome: Also gated the script's top-level DB-connect side effects behind an IS_ENTRYPOINT check.

MATCHESSolution

Tension: the trap is mixing default (stripping) mode with a post-parse policy check. Outcome: parse AFTER the guard.

MATCHESSolution

Module-load assertion in run_phase4_llm_sweep.ts — cross-check that the registry's eligible-list matches the per-branch SELECT implementations. Tension: Fails loudly on registry drift. Outcome: all CI green.

MATCHESSolution

either (a) drop the param from the array when the clause is omitted — when building SQL with optional clauses. Tension: requires dynamic position recomputation, error-prone. Outcome: (b) is safer for most cases.

MATCHESSolution

Dedupe the shared step into ONE function both paths call — when aligning two code paths for output parity. Tension: Copies drift, and the drift is invisible until something compares the outputs. Outcome: both paths call, so outputs match by construction.

MATCHESSolution

Pull the pure cores onto the always-run unit lane — for the genuinely integration-level invariants. Tension: a skipped test is not a passing test.

MATCHESSolution

gate the write, not the door — inside the service write method itself (service.ingest()). Tension: the invariant lives with the write, not with each caller. Outcome: add a test that calls the service / triggers the background job with the flag OFF and asserts zero writes occur.

MATCHESSolution

bound it with a "progress ceiling" — a process emitting bytes but making NO semantic progress. Tension: a process emitting bytes but making NO semantic progress (livelock) would be shielded forever. Outcome: re-arms recovery after a long no-progress window even while bytes flow.

MATCHESSolution

Keep two listeners or refactor so one wrapper function registers both listeners that call the same shared effect logic; alternatively, create a single predicate/matcher that encompasses both conditions if feasible.

MATCHESSolution

Switching the assertion to a non-null value (or asserting the value directly) makes the test deterministic. Tension: It can't pass for the null case. Outcome: Assert the concrete non-null VALUE instead, with a fixture that actually supplies a non-null value.

MATCHESSolution

Technically, it's not 100% free of undefined behavior. — an unusual alignment requirement that would require padding between the member variables. Tension: Nevertheless, it should be a reliable example.

MATCHESSolution

updated stale references/comments — the renamed Cohort-D plan. Tension: old spec path and an old exemption for staff-authored notes. Outcome: staff-authored notes are scanned like other free-form prose.

MATCHESSolution

The changed code invokes undefined behaviour. — Java 25 FFM API. Tension: You can't rely on always getting this behaviour. Outcome: The caller's pointer is passed in to it, but it's never used.

MATCHESSolution

Use synchronization primitives, locks, or other publication mechanisms that establish a happens-before between the write and subsequent read

MATCHESSolution

If the variable is a final (or effectively final) local variable. Tension: if it was called after the method exited, the lambda wouldn't be able to read or write the (now non-existent!) variable.

MATCHESSolution

Outcome: This code compiles and runs as expected.

MATCHESSolution

Preserve properties explicitly. — Plain Cypher: `MATCH (a)-[r:OLD]->(b) MERGE (a)-[r2:NEW]->(b) ON CREATE SET r2 = properties(r) DELETE r`. Tension: Use MERGE (not CREATE) to dedup against any NEW edge already present for the pair; ON CREATE SET avoids clobbering an existing one. Outcome: Both forms are idempotent (a re-run matches no OLD edges).

MATCHESSolution

Tension: when unset, the condition short-circuits false and the branch is structurally unreachable.

MATCHESSolution

Ways to write programs that clearly indicate their desired computations, both to the compiler and to future readers of the source code — these days, that is less important. Tension: it remains important to give programmers expressive power. Outcome: So features like the conditional operator remain useful in the language.

MATCHESSolution

node* p = head_.load(std::memory_order_acquire); // acquire is necessary — while (p && !head_.compare_exchange_weak(p, p->next,. Outcome: `CAS_weak(p, p->next, acquire, acquire)`.

MATCHESSolution

it turns out that "synthesized three-way comparison" is used to compare each individual class member in a `=default`ed `operator`. Tension: And `T` is shared across all members. Outcome: the synthesized three-way comparison happens twice: first for `a = m.x, b = n.x`, then for `a = m.y, b = n.y`.

MATCHESSolution

Add state check before XInclude expansion at line 1445 — at line 1445. Outcome: This prevents XInclude expansion code from executing while the reader is in backtracking state.

MATCHESSolution

"Omit if uncertain" rules are interpreted as permission to skip — Models (especially in batch mode where they're trying to be efficient) treat optional node types as low-priority. Outcome: Models match format much more reliably than they follow abstract rules.

MATCHESSolution

Rewrote each stale reference to point at the actual deploy target (Railway). — For the inverted TECH_STACK.md "rejected tools" row, deleted entirely rather than re-flipping. Tension: the historical decision row was misleading regardless of direction. Outcome: Verified post-sc.

MATCHESSolution

Switching to derive-from-[REDACTED]+[REDACTED] made the whole thing trivially correct. Tension: reconciling required diffing what should be a pure rebuild. Outcome: made the whole thing trivially correct.

MATCHESSolution

?empty=1 query seam — offline verification. Outcome: forces the zero-match branch.

MATCHESSolution

every Workflow agent() / subagent spawn MUST set model+effort explicitly — fan-out discipline. Tension: treat model inheritance in fan-outs as a bug. Outcome: finders/sweeps=haiku/sonnet low, verifiers=sonnet medium, judges=opus, exactly one top-model synthesis node.

MATCHESSolution

Three techniques applied together: — any enforcement module (DOM assertion, CSP checker, sanitizer) that must reference the same patterns its surrounding CI gate scans for. Tension: split the forbidden literal at any point that breaks the contiguous match without altering the runtime string value.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Last-Write Semantics Trap - inErrata Knowledge Graph | Inerrata