Repository navigation
Check for redundant implications - #445
Merged
Merged
Conversation
ScriptRaccoon
marked this pull request as ready for review
October 29, 2026 22:23
ScriptRaccoon
force-pushed
the
redundant-implications
branch
from
October 29, 2026 22:24
3084a82 to
6e6b2b8
Compare
ScriptRaccoon
force-pushed
the
redundant-implications
branch
from
October 29, 2026 23:02
6e6b2b8 to
da47680
Compare
also: - turn some equivalences into one-sided implications to avoid redundancy - remove some redundant conclusions of implications - restructure some implications to avoid redundancies - mark the other reported implications, that are interesting or necessary, as non-redundant - add alternative proof for binary products + pullbacks => equalizers (the one generated by the system) - clarify some proofs - improve references for `grothendieck_topos_consequence`
ScriptRaccoon
force-pushed
the
redundant-implications
branch
from
October 30, 2026 08:56
da47680 to
e2e5e49
Compare
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.
This PR adds a check for redundant implications to
pnpm db:test, analogous to the existing check for redundant property assignments (cf. #155), and removes or restructures the implications it reported. It resolves #16.Redundancy check for implications
pnpm db:testnow fails if an implication can be deduced from the other implications. This also covers single conclusions of an implication and single directions of an equivalence. Each redundant implication is listed once, together with a deduction from the other implications.check_redundancy: false, as for property assignments. This is intended for implications that state a definition or a standard characterization, and for those whose removal would lead to an overly complex automatic deduction.Data changes
check_redundancy: false(53 in total), e.g. "cartesian closed + strict terminal object ⟹ thin".Removed implications
The following (in some cases, non-trivial) implications are among those that have been removed. It is remarkable that the system deduces them from the other implications in a non-circular way:
Search page
If the search requirements are inconsistent, each step in the proof of the contradiction now links to its implication. The search and the new redundancy check use the same deduction code.