Reduce number of arguments of recognition methods#355
Reduce number of arguments of recognition methods#355
Conversation
7d3d0bb to
418fbc1
Compare
|
Apparently, |
|
@SoongNoonien not sure what you mean by " Direct access to "components" of objects in GAP is via Anyway presumably you are getting or seeing an error somehow somewhere, could you clarify? I didn't see any such error in the CI logs (Watch out for syntax errors etc. when loading GAP / the packages). Although, this PR now has a merge conflict again, so CI tests won't run until that's resolved. |
I'm talking about this error: Currently, I write |
|
|
|
I've resolved the merge conflict. The recommend way is indeed |
So yeah, that's not a recognition method. Indeed, the code in But using |
|
Ok, this seems to have cleared these errors. I'll work on the other ones and reduce the diff later on. |
21bd026 to
40182b0
Compare
Right now recognition methods take two arguments: `ri` and `G`.
But `G` is always identical to `Grp(ri)`. Alas, not everyone will
know this, e.g. I am re-discovering this every time I start
digging into recog again. This can be very confusing ("why are
both these groups around? Is there any subtle difference????").
One could solve that by trying to document this, but I think it is
much better to just remove the second argument.
b239c2e to
6b12678
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #355 +/- ##
==========================================
+ Coverage 73.01% 73.04% +0.03%
==========================================
Files 44 44
Lines 18370 18414 +44
==========================================
+ Hits 13412 13451 +39
- Misses 4958 4963 +5
🚀 New features to boost your workflow:
|
Right now recognition methods take two arguments:
riandG. ButGis always identical toGrp(ri). Alas, not everyone will know this, e.g. I am re-discovering this every time I start digging into recog again. This can be very confusing ("why are both these groups around? Is there any subtle difference????"). One could solve that by trying to document this, but I think it is much better to just remove the second argument.This is incomplete, a lot more needs to be changed in methods. This can only be partially automated with classical scripts (and I don't trust AI to do this), but it's actually not hard to do. Alas: I'd like to defer this until after merging PR #330 (and perhaps a few others, to minimize conflicts for those).
Resolves #185 (once it is done)