Precision fixes for some code dealing with ArbField/AcbField #1707
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1580 reported by @fredrik-johansson which was introduced by PR #1367 resp. commit eefcf5b.
I am not quite sure if the test I added is "right" to verify we get the desired precision, if someone can suggest a better methods, I'd be obliged. (I don't quite understand why$\log_{10}(2^{333})$ but couldn't find a good way).
radius(y)
suggest a precision of about1e-113
while the printing says... +/- 1.79e-101
-- I wanted to check the latter, which nicely patchesI also fixed a few other things in the same PR but did not add any tests for them.
Moreover, a few of the changed functions should probably get variants for
RealField
andComplexField
..