changed an IsGeneratorsOfMagmaWithInverses
method ...
#4485
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.
... that deals with collections of
IsMagmaByMultiplicationTableObj
:Really check that the given elements are invertible. Up to now, the method was wrong.
I stumbled over the problem in the context of pull request #4373 and issue #4480.
Here is an example.
Note that the filter
IsMultiplicativeElementWithInverse
does not mean that the element in question necessarily has an inverse, see the documentation.After the change, the method can still give a wrong answer if it is called in the case of nonassociative multiplication. Currently (see issue #4480) there is a discussion how to deal with this situation.
(We have quite a few correct methods for
IsGeneratorsOfMagmaWithInverses
; the default method prints a warning if it cannot returnfalse
. The interpretation is that one should provide a meaningful method for the concrete situation if one sees this warning. The method which is now to be changed serves the purpose to avoid the warning. Eventually it would be good to turn it into a safe method.)