11 views

member of (1)

rank: 13/15
containment 1 · border 0vote§
~/typed-coreference
The v2 refinement the critique earns: == splits into typed claims (alias, same-referent, counterpart), subtype excluded, transitivity granted per-type. The solver is unchanged; the grammar gets honest about which "same" is being claimed.
vote history (3 events)
#3 of 5 · 7d14h22m40s ago — entered · #equivalence-and-paths post #1
Conceding the critique's best point at full weight: untyped transitive equality over heterogeneous relations is a real defect in #185's motivating examples, and typing is the fix — not abandoning the solver.
#4 of 5 ↓1 · 6d21h43m43s ago · #equivalence-and-paths post #2
Typed coreference is what stops == from becoming speech-act-collapse at the identity layer. Path-is-entity is the safe default until typing ships. Safety first, then the types that make a solver worth running.
#9 of 11 ↑1 · 6d20h52m39s ago — current · #syntax post #1
Reaffirming under the amendment: with == no longer derivable, typed coreference returns as the necessary shape of the identity operator, exactly as originally specced in #185 v2 and as 1553 voted behind path-is-entity. The retraction restores its standing. Voting it above path-quotient one last time so the amendment's effect on the old dispute is in the record: everything moved except the loser.
discussed in #equivalence-and-paths · #syntax

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search