Restrict generic ==(x::NCRingElem, y::NCRingElem) fallback#2212
Conversation
|
Sorry, I don't fully understand what the additional branch is supposed to do. Is there something missing at the moment? |
|
I think it should be triaged, and documented: what is OUR intended behaviour for == between arbitrary pairs? The default of false is due to julia - and has bitten be a couple of times. Independently, we probably should add === as a first test? |
659d91f to
3204661
Compare
|
@thofma yes, sorry, there was supposed to be another But the real change was that |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2212 +/- ##
==========================================
- Coverage 88.08% 88.07% -0.02%
==========================================
Files 126 126
Lines 31729 31729
==========================================
- Hits 27949 27944 -5
- Misses 3780 3785 +5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I like the tests, since this application appears in the "real world". |
|
We discussed this during triage, and my understanding is that in the end we agreed (even @thofma) that we could try to go on with this. This example from PR #285 still works even with this PR here: julia> a = zero_matrix(ZZ, 2, 3)
[0 0 0]
[0 0 0]
julia> b = zero_matrix(ZZ, 3, 3)
[0 0 0]
[0 0 0]
[0 0 0]
julia> a in [b, a]The relevant test should be re-enabled. (@thofma or anyone else will correct me if I misrepresented anything unwittingly) |
|
Looks good. Also still works. |
So far this method default to returning `false` if it failed to promote the arguments into a common ring. That lead to situations were comparisons between unrelated rings seemed "possible" but returned surprising results.
700675b to
fc670f5
Compare
|
Resolve the merge conflicts and added some more matrix tests. This is good to go from my viewpoint. |
Co-authored-by: Lars Göttgens <lars.goettgens@rwth-aachen.de>
So far this method default to returning
falseif it failed to promote the arguments into a common ring. That lead to situations were comparisons between unrelated rings seemed "possible" but returned surprising results.Motivated by oscar-system/Singular.jl#908, that is:
See also #1853, #1854, #1873 for related unmerged PRs ...
Let's see if this one is less problematic/painful/controversial/... sigh
CC @lgoettgens @thofma @fieker