The residual case of epsilon/split synchronization #
This file separates the easy paired-read contradiction from the genuinely interval-sensitive paired-split case. In particular, the useful endpoint form below avoids rebuilding a list completion merely to exclude a nonempty zero-visible return to the same physical list cut.
A useful epsilon-bearing tail cannot return to the same physical list
head. This is the direct-usefulness variant of
epsilonBearing_sameListCutTail_false: the caller may already have the
combined child-completion/continuation path.
The paired-read constructor of an epsilon/split tail is impossible. Both read anchors have the same deterministic output cut, so the bearing tail is a nonempty useful return to that same physical list head.
The counted operational content left by the paired-split constructor.
The first two intervals are the two completed single source top next
returns. The last retained run is the genuinely nonempty epsilon-bearing
tail from the first return endpoint to the epsilon child cut.
Equations
- One or more equations did not get rendered due to their size.
Instances For
Every epsilon/split tail reduces to the counted paired-split residual.
The root constructor is excluded by the right list index, while the read
constructor is discharged by epsilonBearing_pairedRead_false.