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
When using lambdify with cse=True, it appears that the expression might get evaluated before the printer generates the code.
In the following example I'm using mpmath because it uses arbitrary precision floating point, hence it is able to deal with huge numbers. But the following behavior also happens when using Numpy/Scipy or math.
Why am I using cse=True? A user can pass any expression to my application, which must be evaluated as quickly as possible. My application assumes that cse=True is not going to make things worst: sometime it is useful, other times it is superfluous, as it should be in following example. Instead, here it is making things worse:
When using
lambdify
withcse=True
, it appears that the expression might get evaluated before the printer generates the code.In the following example I'm using
mpmath
because it uses arbitrary precision floating point, hence it is able to deal with huge numbers. But the following behavior also happens when using Numpy/Scipy or math.Why am I using
cse=True
? A user can pass any expression to my application, which must be evaluated as quickly as possible. My application assumes thatcse=True
is not going to make things worst: sometime it is useful, other times it is superfluous, as it should be in following example. Instead, here it is making things worse:The text was updated successfully, but these errors were encountered: