-
-
Notifications
You must be signed in to change notification settings - Fork 553
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
Coercion between algebraic polyhedra fails #28776
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:3
As was pointed out to me, it is not desirable to coerce number fields to the smallest field in general. As it is not canonical, fragile and expensive. However, it seems to be desirable for polyhedra, isn't it? Would it make sense to implement that somewhat as a standard behavior, e.g. that a polyhedron over QQ[sqrt(2)] and one over QQ[sqrt(3)] are coerced to one over QQ[sqrt(2) + sqrt(3)]? |
This comment has been minimized.
This comment has been minimized.
comment:5
Ticket retargeted after milestone closed |
comment:6
Moving tickets to milestone sage-9.2 based on a review of last modification date, branch status, and severity. |
comment:8
Moving this ticket to 9.4, as it seems unlikely that it will be merged in 9.3, which is in the release candidate stage |
comment:9
Setting a new milestone for this ticket based on a cursory review. |
comment:10
Stalled in |
For the following polyhedra all things involving coercion fail.
It seems to boil down to two issues:
P.base_extend(P1.base_ring())
doesn't do anything, see Polyhedra coercion of base rings fails for number fields #28770,Do we want to change that design for polyhedra? I think it is reasonable to coerce polyhedra over number fields by default. At least when there is exactly one composite field.
Depends on #28770
CC: @jplab @LaisRast @videlec
Component: geometry
Keywords: algebraic polyhedra, quadratic fields
Issue created by migration from https://trac.sagemath.org/ticket/28776
The text was updated successfully, but these errors were encountered: