> Can we agree on discarding the current implementation for now and then
> rewriting it based on a tree builder instead of a parser wrapper?
Only if it actually brings something (feature-wise, performance-wise,
maintenance-wise, whatever) that the current implementation doesn't
have.
Otherwise, I'd rather check in the simple inheritance-to-composition
change.
I'm sorry that you noticed this after the alpha. I would have had a
lower threshold for changes if you had manifested when I proposed the
feature.