-
-
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 quadratic fields fails #28774
Comments
New commits:
|
Commit: |
Branch: public/28774 |
comment:3
Many failing tests and various places. |
Changed author from Jonathan Kliem to none |
This comment has been minimized.
This comment has been minimized.
comment:6
This seems like it would be a good idea to post to sage-devel if only just to understand the rationale of the current state. |
This comment has been minimized.
This comment has been minimized.
Changed branch from public/28774 to none |
Changed commit from |
comment:8
Perhaps a more useful error message could be given here? The hint about using composite fields seems especially helpful. |
comment:9
Yes, I was thinking about this as well. Wasn't sure where to put this. I could give such a message in the |
Dependencies: #28778 |
Branch: public/28774-new |
Commit: |
comment:11
This is the best I can come up with. To my understanding coercion of two number fields is only possible, if they are both embedded into Raising an error or a warning does not work, as it is being suppressed. This depends on #28778 now, as this fixes an error (along the way), where the pushout of two number fields embedded into New commits:
|
comment:12
Ticket retargeted after milestone closed |
Author: Jonathan Kliem |
comment:15
Patchbot says:
in particular:
and
and the patchbot also says pyflakes warnings:
and
|
comment:16
I posted about this on sage-devel https://groups.google.com/d/msg/sage-devel/oSFceE75pWU/K-akRxS6BAAJ. At the moment it looks like there isn't much interest. I'll wait a day and if nothing shows up, we can just close this here as invalid. |
Changed author from Jonathan Kliem to none |
Changed commit from |
Changed branch from public/28774-new to none |
comment:18
ok |
Reviewer: Sébastien Labbé |
This is by design, as it is hard to guess the users intentions:
AA
for exploratory work, as it is precise but possibly very slow. Exact conversion toAA
works:composite_fields
:However, there is a choice involved in picking the common number field, which is up to the user.
Depends on #28778
Component: number fields
Keywords: quadratic field, embeddings
Reviewer: Sébastien Labbé
Issue created by migration from https://trac.sagemath.org/ticket/28774
The text was updated successfully, but these errors were encountered: