an-cabal/an-rope

Do we really need both `Rope` and `Node` types?

Opened this issue · 0 comments

hawkw commented

At first glance, it looks like the Rope type is just a wrapper around Node, and all of its methods delegate out to Node's. Can we easily de-complexify Rope by removing the Rope struct and promoting Node to Rope?