You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is non negligible because is_exact is called basically each
time an element is constructed or arithmetic is performed. Here we
have a 10% improvement on constructing an element:
Before the patch:
sage: x = P.gen()
sage: y = x+1
sage: %timeit R(x,y,coerce=False)
625 loops, best of 3: 17.7 µs per loop
After the patch:
sage: x = P.gen()
sage: y = x+1
sage: %timeit R(x,y,coerce=False)
625 loops, best of 3: 16 µs per loop
Before the patch:
After the patch:
Thank you Simon King for #11115!
This is non negligible because
is_exact
is called basically eachtime an element is constructed or arithmetic is performed. Here we
have a 10% improvement on constructing an element:
Before the patch:
After the patch:
CC: @simon-king-jena
Component: performance
Author: Nicolas M. Thiéry
Reviewer: David Loeffler
Merged: sage-5.0.beta9
Issue created by migration from https://trac.sagemath.org/ticket/12527
The text was updated successfully, but these errors were encountered: