Repository navigation
javascript: a computed table read defaulted inline ((t[k] || d)()) or by reassignment reports the default as the only callee #1727
Description
Symptom: a dispatch-table read with a computed key that is defaulted inline or by reassignment reports the default as the only callee ([resolved]), and path calls the caller and the table's functions independent. The const h = t[k] || d; h() form (#931) and the ?? / ternary forms are already one of a set.
function f1(x) { return x; }
function f2(x) { return x; }
function fb(x) { return x; }
const local = { f1, f2 };
export function w1(k, s) { return (local[k] || fb)(s); } // inline default
export function w2(k, s) { let h = local[k]; if (!h) h = fb; return h(s); } // default by reassignmentaxiomcode impact fb: w1 and w2[resolved](known_edge, single target)axiomcode path w1 f1: "the two are independent in this graph"
Expected: both sites one of a set → f1, f2, fb, as for const h = local[k] || fb; h(s).
Actual: known_edge → fb only; f1/f2 get no caller from them. Seen with the table in the same file and imported from another module.
Activity
swapnilpaliwal-sd commentedon Sep 29, 2026
This issue now tracks 1 related issues about JavaScript dispatch through computed tables, React context and connected props (#1751). Those issues are closed as duplicates of this one; each keeps its own description and reproduction. The group is fixed together in one change, and this issue closes when that change reaches the release branch.
swapnilpaliwal-sd commentedon Sep 29, 2026
Fixed by #1767 (merged into 0.1.8).