Generalized Reedy categories, Direct categories#571
Open
Conversation
Member
New pages
Changed pages
|
ncfavier
reviewed
Nov 29, 2025
Suggested-by: Naïm Camille Favier <n@monade.li>
ncfavier
approved these changes
Nov 29, 2025
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.
Description
Just some basic definitions about Reedy/direct categories, along with a theorem about reflective subcategories of reedy categories.
Notes
It might be worth omitting "generalized" from both of these definitions, and calling the strict variants "skeletal Reedy" and "skeletal direct". I've opted to keep the same nomenclature as the literature here, but we almost always want to use the generalized versions.
Checklist
Before submitting a merge request, please check the items below:
support/sort-imports.hs(ornix run --experimental-features nix-command -f . sort-imports).