…ecs (for now).
…e., find methods which are identical except for one node, find methods which are identical except for two nodes, etc., for any N nodes. What would be really cool is if it could recognize when those diff nodes were method calls vs. literals, e.g., strings, numbers, etc., because literals are easier to parameterize.
…a complete straw man.
…creating classes even though the effect is essentially the same. Just took less code and required me to change less stuff.
…nyms(). For some reason diff-node spec failing so I had to switch the order of the methods in the ruby2ruby output. That makes no sense and is a flaw not in my code but in my testing strategy. I should be testing on the data, not the pretty-printing. Fail! Well whatever, I'll fix it later.
…is means you can have two methods - well, you'll see it in the spec data dir, but basically - you can have two methods which differ only by one thing, e.g., a literal or a method call, and if those two methods exist which only differ by one thing, Towelie goes hey, you got two methods here that only differ by one thing. The theory of course is that highly similar methods are prime targets for refactoring. The existing implementation is clumsy, but should improve soon I hope.
…st be tired or something.
…rse(). I'm damn near certain I'll refactor that soon.
…thods from within classes, and methods from within modules.
Probably the next step is for the parsing process to retain some metadata, i.e., filename - otherwise this info is of limited usefulness.