Isuru Fernando
Isuru Fernando
Or, we can extend `create` method already defined for all functions to all of `Basic`.
It's for language bindings where users wants to manipulate subexpressions. For eg: https://discourse.julialang.org/t/symengine-dropping-terms-in-a-polynomial-with-near-zero-coefficients/17391
You should use `dFx1(x1=>x1_val, x2=>x2_val)` and similarly for `newx1`. Problem with not using these keyword args (is that the Julia name?) is that without them the number of variables depend...
SymPy caches the results of those methods. Without the cache, here's what the timings look like, ```python In [1]: import random, sympy, symengine In [2]: %timeit symengine.Integer(random.randint(1, 1e6)) 1.95 µs...
With setup code removed from timings there's still a slowdown ```python In [1]: import random, sympy, symengine In [2]: %%timeit a=random.randint(1, 1e12) ...: symengine.Integer(a) ...: ...: 1.51 µs ± 164...
One bottleneck is that we convert Python integers to string and pass them to the C++ library. This can be fixed though.
@raphaelquast, the pickle file for `llvm` backend is platform dependent. You won't be able to save in linux and load in macos
`is_number` and `is_Number` difference is consistent with sympy. Names with capitals indicate a class and the attribute is true only if the expression is an instance of that class I...
Please open this issue in vcpkg issue tracker.
It's not supported directly yet, but indirectly from https://github.com/korsbo/Latexify.jl,