split: add split * and split + to iterate over top-level conjunctions#1015
Merged
Conversation
…ions `split *` peels every top-level /\ and && until the head is no longer a conjunction; it is a no-op when the goal is not a conjunction. `split +` is the same but errors if the outermost goal is not a conjunction. No unfolding; only the SFand head is matched. For asymmetric && (`a && X`), the right side may depend on `a`, so the recursion intros `a` as a hypothesis, peels X, then re-generalizes the hypothesis over every leaf produced. This mirrors how plain `split` handles a single &&, and keeps the semantics sound when /\ or && is nested under &&. E.g. `a && (b /\ c)` yields three subgoals `a`, `a => b`, `a => c`.
Gustavo2622
approved these changes
May 26, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to no response for status checks
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
2 participants
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.
split *peels every top-level /\ and && until the head is no longer aconjunction; it is a no-op when the goal is not a conjunction.
split +is the same but errors if the outermost goal is not a conjunction. No
unfolding; only the SFand head is matched.
For asymmetric && (
a && X), the right side may depend ona, so therecursion intros
aas a hypothesis, peels X, then re-generalizes thehypothesis over every leaf produced. This mirrors how plain
splithandles a single &&, and keeps the semantics sound when /\ or && is
nested under &&. E.g.
a && (b /\ c)yields three subgoalsa,a => b,a => c.