-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mark as deleted #32
Mark as deleted #32
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #32 +/- ##
==========================================
+ Coverage 88.56% 89.20% +0.64%
==========================================
Files 12 11 -1
Lines 883 954 +71
==========================================
+ Hits 782 851 +69
- Misses 101 103 +2
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly looks good, just a couple of comments.
rendering parts rename rebase cleanup more export
These macros are in Catlab, not ACSets.
Also, expand and clean up docstring for these types.
This had effectively disabled all the other tests!
Besides being uncovered by the tests, it's not very natural since the keys of the column are generally unordered.
The abstract base type is now called simply `PartsType`.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kris-brown, apart from this last question, I'm happy with this PR!
An alternative to representing the set of parts with an int (i.e.
1:n
), this PR is a move towards generalizing that data structure. We start with just supporting eitherInt
orBitSet
as a parameterpart_type
when making an ACSet type.Deletion is trivial for BitSet-backed ACSets but the work is done in
gc!
for garbage collection.Currently there is nothing at the type level to distinguish ACSets with one part type vs another. It is assumed (though not presently enforced) that all parts must be the same type.