#11670: fix number fields being unique parents -- this got broken over the years
-------------------------------------+-------------------------------------
Reporter: was | Owner: davidloeffler
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.2
Component: number fields | Resolution:
Keywords: | Merged in:
Authors: Julian Rueth | Reviewers: Simon King
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/saraedum/ticket/11670 | 70702aa690a31cc36b9febe36462c67ebd57dcee
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by pbruin):
Replying to [comment:28 saraedum]:
> I agree that it makes sense that two number fields are different if they
have a different structure. I had a feeling that this would break too much
existing code, though.
Hmm, I wonder if one could test easily if this would indeed be a problem
(within the Sage library, say).
> I think it is a natural first step to rewrite number fields to use a
factory and make them unique parents (this ticket).
Doesn't "unique parents" mean precisely that parents are equal if and only
if they are identical (see the third paragraph of
[http://www.sagemath.org/doc/thematic_tutorials/coercion_and_categories.html
this page])?
(I'm only starting to understand the finer points of all this; I thought
understanding the situation for number fields would be a good first step
towards the similar problem for elliptic curves in #11474.)
--
Ticket URL: <http://trac.sagemath.org/ticket/11670#comment:29>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
