deal with unwanted side-effects of #3006 #5336
Merged
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.
DeclareHandlingByNiceBasis
implyIsFreeLeftModule
. This was the case before the changes from Forbid installing new implications to representations usingInstallTrueMethod
#3006, and this change fixes the problem described in Regression inDeclareHandlingByNiceBasis
/InstallHandlingByNiceBasis
#5322, as I had sketched in the discussion of fix the documentation ofDeclareHandlingByNiceBasis
#5325.DeclareHandlingByNiceBasis
#5325).IsHandledByNiceBasis
by 2. Then we get back to the rank before the changes from Forbid installing new implications to representations usingInstallTrueMethod
#3006. This way, the\in
method with second argument inIsFreeLeftModule and IsHandledByNiceBasis
is again ranked higher than the one with second argumentIsFreeLeftModule and IsFiniteDimensional
. The bug described in issue Regression: recent changes caused packageguava
to fail its test suite #5334 which has been found because of the reordering of these two methods (due to Forbid installing new implications to representations usingInstallTrueMethod
#3006) gets fixed via pull request Fix a case whereCoefficients(B,v)
returned a list instead offail
although the vectorv
did not lie in the underlying vector spaceV
ofB
#5335, now we can return to the better method ordering. (I do not like uprankings, but I have no better idea to solve this problem.)