#11869: Horrible bug in number field conversion
-----------------------------+----------------------------------------------
Reporter: jdemeyer | Owner: davidloeffler
Type: defect | Status: needs_info
Priority: major | Milestone: sage-4.7.2
Component: number fields | Keywords: coercion
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies: #11873, #11876
-----------------------------+----------------------------------------------
Comment(by jdemeyer):
Replying to [comment:22 SimonKing]:
> I am a bit confused: In the keywords, you name it "coercion". But in
your example, you just talk about conversion. If it really is a coercion
(please check: Does that conversion happens implicitly?) then I agree it
is a bug.
It certainly ''used to be'' a stupid "conversion".
My patch actually implements something which is much closer to coercion.
Essentially, it is coercion on ''subfields'' of the given number fields.
Suppose I have two number fields `L1` and `L2` sharing a common subfield
`K`. Even if there is no coercion map from `L1` to `L2`, there is a
coercion between the subfields `K` of `L1` and `K` of `L2`.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11869#comment:23>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
