-
-
Notifications
You must be signed in to change notification settings - Fork 535
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
Fix __getitem__ and slicing for p-adics #13300
Comments
comment:1
The attached file (which has an extra 3 in the filename, sorry) fixes this. To be consistent, indexing gives elements in the residue field. Mathematically, this seems to make sense, but is this really what one wants? I'm running all doctests now to see if this breaks anything. |
comment:2
The doctests worked, so I'm setting this to needs review. |
Author: Julian Rueth |
comment:4
Attachment: trac_13330.patch.gz I don't think that giving elements of the residue field is what we want, though I agree that the current behavior for unramified extensions is silly. I would like to be able to have
without having to lift from the residue field. Of course, sometimes you want to get at the coefficient of
What if we used a similar tuple indexing scheme for p-adic elements? For example:
The parent of z[i], z[i,T] and z[S,T] (for integer i and slices S,T) would be the unramified extension; the parent of z[i,j] and z[S,j] would be the ground field (or ring). Negative indices would never be considered as counting backward from a length, even for ring elements. What do you think? |
comment:8
Let's think about this again once #14304 has been merged. |
comment:10
I like your proposal. Let's discuss this at one of the IRC sessions. |
This is a meta-ticket to track progress on fixing
__getitem__
and slicing of p-adic elements and their .expansion().Depends on #13299
Depends on #14304
Depends on #26406
Depends on #26407
Depends on #26408
Component: padics
Author: Julian Rueth
Issue created by migration from https://trac.sagemath.org/ticket/13300
The text was updated successfully, but these errors were encountered: