Beautifying, reformatting or otherwise "improving" code could potentially change its meaning. Neither unit tests nor visual inspection suffices to show that the old code is equivalent to the new.
Leo should have a script or command that will cache the underlying meaning: either an Ast or opcodes. The workflow would be: - Capture the meaning of files before they change. - Beautify or otherwise change the files. - Compare the old or new meanings. This would be so much safer than inspecting diffs. I'll see what I can do today... This would be an important tool. With it, ambitious pep-8 related transformations could be undertaken safely. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
