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 subfield methods compatible, implement for more fields #30171

Open
mkoeppe opened this issue Jul 18, 2020 · 6 comments
Open

Make subfield methods compatible, implement for more fields #30171

mkoeppe opened this issue Jul 18, 2020 · 6 comments

Comments

@mkoeppe
Copy link
Member

mkoeppe commented Jul 18, 2020

For finite fields, #27949 added a subfield method.

Absolute number fields have a subfield method, but it is incompatible with the one added for finite fields.

sage: K.<sqrt2> = QuadraticField(2)
sage: K.subfield(1)
(Number Field in sqrt20 with defining polynomial x - 1 with sqrt20 = 1,
 Ring morphism:
   From: Number Field in sqrt20 with defining polynomial x - 1 with sqrt20 = 1
   To:   Number Field in sqrt2 with defining polynomial x^2 - 2 with sqrt2 = 1.414213562373095?
   Defn: 1 |--> 1)

#23245 notes that RationalField lacks many methods of general number fields, include subfield

See also: #14956, #6092

CC: @kliem @videlec @kwankyu @tscrim @fchapoton

Component: algebra

Issue created by migration from https://trac.sagemath.org/ticket/30171

@mkoeppe mkoeppe added this to the sage-9.2 milestone Jul 18, 2020
@mkoeppe

This comment has been minimized.

@kwankyu
Copy link
Collaborator

kwankyu commented Jul 20, 2020

comment:2

Assuming that we want them compatible, I am leaning to the version of the finite fields subfield() methods, where the ring morphism is not returned as a coercion map is available indirectly. But heavy users of number fields might have different opinions.

@mkoeppe
Copy link
Member Author

mkoeppe commented Jul 20, 2020

comment:3

A way to make them compatible would be to have an option return_map.

@kwankyu
Copy link
Collaborator

kwankyu commented Jul 20, 2020

comment:4

Replying to @mkoeppe:

A way to make them compatible would be to have an option return_map.

More common name for the option is probably map=True.

@mkoeppe
Copy link
Member Author

mkoeppe commented Jul 20, 2020

comment:5

Sounds good

@mkoeppe mkoeppe modified the milestones: sage-9.2, sage-9.3 Oct 24, 2020
@mkoeppe
Copy link
Member Author

mkoeppe commented Mar 24, 2021

comment:7

Sage development has entered the release candidate phase for 9.3. Setting a new milestone for this ticket based on a cursory review of ticket status, priority, and last modification date.

@mkoeppe mkoeppe modified the milestones: sage-9.3, sage-9.4 Mar 24, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.4, sage-9.5 Jul 19, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.5, sage-9.6 Dec 18, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.6, sage-9.7 Apr 1, 2022
@mkoeppe mkoeppe modified the milestones: sage-9.7, sage-9.8 Aug 31, 2022
@mkoeppe mkoeppe modified the milestones: sage-9.8, sage-9.9 Jan 7, 2023
@mkoeppe mkoeppe removed this from the sage-10.0 milestone Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants