-
Notifications
You must be signed in to change notification settings - Fork 57
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
p-adics done right #1746
p-adics done right #1746
Conversation
7d2bee1
to
3f91824
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1746 +/- ##
==========================================
+ Coverage 85.09% 85.32% +0.22%
==========================================
Files 95 95
Lines 36917 36903 -14
==========================================
+ Hits 31416 31487 +71
+ Misses 5501 5416 -85 ☔ View full report in Codecov by Sentry. |
fcc3b80
to
de68ed3
Compare
I think I have now everything we discussed. |
Looks good, let's discuss the Hecke breakage tomorrow. |
return g | ||
end | ||
|
||
function with_precision(f, K::QadicField, n::Int) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a869897
to
c6dd543
Compare
Remove/deprecate some particularly "interesting" (and unused) functionality
Also make the precision a keyword argument
They redirect to `divexact` and this throws an error.
12590b2
to
cc2b639
Compare
This is good to go from my side. It would be good to have a patch release with this, so that I can use it in Hecke. |
Very good, thanks |
HeckeMoreStuff
to the correct file + some testspadic_field
andqadic_field
where the precision is a keyword argumentprecision
keyword arguments to all constructors which take exact inputprime_field
(should never have been called like that) orlift(::PadicFieldElem)
(lifts to ZZ, so one should calllift(ZZ, ...)
) + more.