Repository navigation
docs(refactor): file R13 — one expression evaluator, the active works… - #81
Merged
Merged
Conversation
…tream WHERE and the value evaluator each implement every boolean operator, with different NULL semantics and three separate truth collapses, so one predicate answers differently in WHERE, HAVING, SELECT and JOIN ON. Probing found four live divergences (HAVING NOT over NULL, SELECT IN with NULL, JOIN pairing NULL keys, P48). R13 records the target shape (one evaluator, NULL as UNKNOWN, one collapse per filtering site) and six slices in the R10 pattern: pin, make the value evaluator three-valued (= P48), unify construction, then retire WHERE's arms one operator at a time as provable no-ops. SQL_PARITY's fix order now makes R13 NEXT, with the working rule that evaluation-touching parity fixes land as R13 slices. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01GpuTexUeuyuAdmDsukMTRW
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…tream
WHERE and the value evaluator each implement every boolean operator, with different NULL semantics and three separate truth collapses, so one predicate answers differently in WHERE, HAVING, SELECT and JOIN ON. Probing found four live divergences (HAVING NOT over NULL, SELECT IN with NULL, JOIN pairing NULL keys, P48).
R13 records the target shape (one evaluator, NULL as UNKNOWN, one collapse per filtering site) and six slices in the R10 pattern: pin, make the value evaluator three-valued (= P48), unify construction, then retire WHERE's arms one operator at a time as provable no-ops. SQL_PARITY's fix order now makes R13 NEXT, with the working rule that evaluation-touching parity fixes land as R13 slices.
Claude-Session: https://claude.ai/code/session_01GpuTexUeuyuAdmDsukMTRW