Skip to content
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

Make comparison of polynomials error if parent check fails #1800

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

joschmitt
Copy link
Collaborator

One way to resolve oscar-system/Oscar.jl#4107 . Let's see what CI says.

Copy link

codecov bot commented Sep 19, 2024

Codecov Report

Attention: Patch coverage is 66.66667% with 4 lines in your changes missing coverage. Please review.

Project coverage is 88.13%. Comparing base (63d54c2) to head (58323e7).
Report is 7 commits behind head on master.

Files with missing lines Patch % Lines
src/MPoly.jl 0.00% 2 Missing ⚠️
src/generic/MPoly.jl 66.66% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1800      +/-   ##
==========================================
- Coverage   88.14%   88.13%   -0.01%     
==========================================
  Files         119      119              
  Lines       29986    29981       -5     
==========================================
- Hits        26430    26424       -6     
- Misses       3556     3557       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

src/MPoly.jl Outdated Show resolved Hide resolved
@lgoettgens lgoettgens closed this Sep 20, 2024
@lgoettgens lgoettgens reopened this Sep 20, 2024
Copy link
Member

@fingolfin fingolfin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am fine with this in principle, although I am not sure how useful it is in general. But there definitely is no harm.

src/MPoly.jl Outdated Show resolved Hide resolved
@joschmitt
Copy link
Collaborator Author

I am not sure how useful it is in general

To me, it sounds reasonable to throw an error if a comparison does (mathematically) not make sense instead of just saying false. I probably don't see all the consequences of this statement and we certainly couldn't enforce this consistently in OSCAR though.

Copy link
Collaborator

@lgoettgens lgoettgens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am just artificially blocking this in favor of concluding in triage how to proceed with oscar-system/Oscar.jl#4107 first.

@lgoettgens
Copy link
Collaborator

I would prefer to just implement ==(::AbstractAlgebra.SetElem, ::AbstractAlgebra.SetElem) = error("== is not implemented for the given types") if we wanna have this

@lgoettgens
Copy link
Collaborator

I would prefer to just implement ==(::AbstractAlgebra.SetElem, ::AbstractAlgebra.SetElem) = error("== is not implemented for the given types") if we wanna have this

Triage agreed with this idea

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Comparison of polynomials from different rings throws inconsistently
3 participants