Alessandro Cheli

> I don't see why this code should return true with this change, and I don't think this is because of the capture macro. The matcher is asking whether the...

@peterahrens > ``` > TermInterface.istree(::typeof(qux)) = true > ``` `typeof(qux)` is `DataType`. Doing this breaks a lot of stuff since `istree(x) = istree(typeof(x))` by default. You set everything to be...

> I don't understand why we need to convert functions to symbols and then re-engineer lexical scoping rules. I agree that that mechanism is somehow intricate. There's a big TODO...

> Ah yes, that was a typo. When the typo is corrected, the expression still returns false. Here's the improved steps to reproduce issues This does not work. The capture...

cc @shashi

@peterahrens fixed `println(@capture qux(1, 2) qux(1, 2))` on latest commit on master

It seems to stop working with `Int32`. I have to investigate

@MrVPlusOne this may be useful for your program synthesis use case

Seems it is an issue when building the pattern for the EGraphs backend. Will investigate ASAP.

Seems like complex literals `-1 + 0im` are not e-graph friendly at the moment.