I have been thinking some more and would like to revise my proposal.
The *Modules > Alphabetical* and *Categories > Modules > Alphabetical*
navigation trees handle distinct use cases.
*Modules Case:* when a developer knows the module AND the function one is
looking for (e.g. when referencing
This is really, really hard to do because it would overcomplicate the
language grammar, as it would have to take comments into account at every
step. I am not even sure if it is possible. If someone wants to try it out
though. :)
That's why most tools end-up handling comments on the side,
Hi Steve
The formatter extracts comments from Elixir source like so:
https://github.com/elixir-lang/elixir/blob/9cf118bd123deb945be71bf3ea2b48cd271088f0/lib/elixir/lib/code/formatter.ex#L199-L225
This may help you.
Cheers,
Louis
On Sun, 16 Sep 2018 at 17:59 Steve Morin wrote:
> Wanted to see
Wanted to see what peoples thoughts are about adding comments to the AST.
One use-case is to be able to parse and manipulate Source files outside of just
macros but in that case you would want to be able to preserve comments.
E.g. Read a source file, manipulate it, write that source file
