-
-
Notifications
You must be signed in to change notification settings - Fork 613
Remove confusion in gap interface conversion method #39909
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
base: develop
Are you sure you want to change the base?
Conversation
Documentation preview for this PR (built with commit b7caa35; changes) is ready! 🎉 |
|
||
TESTS:: | ||
|
||
sage: BD._gap_init_() |
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.
you need to copy here the optional tag and the definition of BD
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.
This bug is non-critical, (if I recalled correctly from the last time I work on this) there are too many code that relies on x._gap_()
with no argument does the wrong thing (see the other test failures) and I just haven't gotten around to fix them yet since it sounds like a lot of work.
Maybe it's better to review the dependency (#39905) first (which is ready).
See the documentation changes in the issue below for an explanation why this change is correct. Basically
_gap_
must take in an interface object and return element of that object; while_libgap_
must take no argument and return libgap element.Also make
IncidenceStructure
inherit fromSageObject
— as noted in the documentation ofSageObject
, all objects visible to the user ought to inherit from it.📝 Checklist
⌛ Dependencies
#39905
Not strictly necessary, but useful to see why this change is correct.