Dorgan

Some side effects of this: - We need a custom traversal function instead of relying on `Macro.traverse` - The Zipper API may need to be updated to handle this new...

You can try these changes(with the exception of the `static_atoms_encoder` one) in the [rich_ast](https://github.com/doorgan/sourceror/tree/rich_ast) branch: ```elixir {:sourceror, github: "doorgan/sourceror", branch: "rich_ast"} ``` CC @marcandre

Sigils were changed to `{:"~", metadata, [letter, contents, modifiers]}`

Hi @msaraiva, I don't see these changes applied to the main branch anytime soon, as it's still too experimental and I realize it will take quite some time to find...

@msaraiva I initially intended to apply them in 0.9, but I started to deviate too much from the original goal and I want to have a clearer spec first. There's...

Producing patches like this has some downsides as well. For example, inserting a sibling node could just produce a patch after that node instead of producing a patch for the...

> In the Ruby world, what we ended up doing is organizing string patches as a tree of nested ranges with replacements and/or insertions at either end. Crossing ranges (e.g....

> in Rfx we've been fiddling with approaches for diff and patch. It would probably be good if Rfx and Sourceror used identical or compatible diff/patch strategies. @andyl of course!...

Sourceror does not read the project's `formatter.exs` file. It doesn't accept the `locals_without_parens` option either. This would be a really useful feature for Sourceror, so I'll leave it open as...

Sounds reasonable :)