Francesco Bonazzi

> Do we need a TEdgeValue value? It seems unneeded. It's more generic, you can generalize the class usages to more types. I am opening PRs to SymEngine, but that's...

Added Takeaki Uno's algorithm. New code has not yet been tested.

For completeness, the Python code used to create those files is: ```python from collections import deque def match_root(subject): subjects = deque([subject]) if subject is not None else deque() subst0 =...

@henrik227 @wheerd I am trying to find a way to translate parts of MatchPy into C++ to allow the generated decision tree to be compiled with SymEngine. The generators (functions...

> If you know that you only need one of those two cases, there might be no need to implement yield at all. The commutative matcher in MatchPy makes heavy...

I suggest to create a module with the currently working stuff, which means everything except for the commutative support. The commutative matcher relies a lot on coroutines and it's pretty...

First you have to test whether the current code generator works eighth SymPy. That's probably pretty easy. After that, you need to translate the utility functions into SymEngine. After this...

Rubi has utility functions. The current python translations are in a subfolder of rubi in SymPy.

> Ok, is this the code generator that we need to get working again with SymPy: https://github.com/sympy/sympy/blob/d7a854fb789591114d7d51c3f23bba2fd4d520cc/sympy/integrals/rubi/parsetools/generate_rules.py Well, that's the code translator. It translates the rules from Mathematica to Python....

It's inside MatchPy. Some edits are necessary to use the code generator. There's an open PR somewhere. For C++, the code generator is in symengine.