Complexes transition issues tracker
@ggsmith is already working on this.
Since May 28, 2026.
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
Since there isn't a project board for Complexes, there is a need for a place for people to track which issues related to the Complexes transition are fixed.
A couple to start with:
- [x] `eagonNorthcott` needs to be reimplemented
- [x] `regularity` from Complexes doesn't work over quotient rings (c.f. #3321)
- [ ] `formation(Complex)` needs documentation, and `formation(ComplexMap)` implemented
- [ ] decide the fate of `GradedModule`, which was added as a synonym of `Complex` for a few packages which only needed this symbol as the output of HH, for instance. A better solution might be to create a new GradedModule type in Complexes and overwrite the other symbol, then the documentation would reflect this as well.
- [ ] `[betti, Minimize]` doesn't do anything, nor is it documented in Complexes. Should it be? Same with `[extend, Verify]`
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.