For fun, I turned on DEBUG...

[dalejordan]

and I noticed a few minor problems:

• @debug "updated parents " id g.parents[id] in repair! generates an exception because g has no parents field (anymore).
• @debug(n, " not found in memo") in add! has its arguments reversed.
  I would make a pull request but I'm not sure how to fix the first problem. Still learning how this all works.

I think it might be useful to add some simple statistics gathering about how many adds, merges, etc. are performed;
a less verbose tracing facility than debug would be useful for those wondering how it all really hangs together.

[0x0f0f0f]

good catch! updated parents have to go directly into repair! since parents are now stored per-enode and not globally in the egraph! would you suggest me any package for defining customizable log levels? never really went deep in logging with julia

[dalejordan]

I looked more deeply into stdlib Logging and it looks like it's gloriously flexible and almost painless with LoggingExtras.jl addons.
I will put together a prototype for tracing and stats (after I figure out a reasonable UI) for your perusal.

[0x0f0f0f]

@dalejordan still interested ?

[0x0f0f0f]

#169

[0x0f0f0f]

Better debugging now in #177