Rewriting Go source code with AST tooling

eli.thegreenplace.net

49 points·ingve··9 comments

Go AST was never really designed for re-writing of the source. Comments are stored by their byte offset instead of attached to nodes, so re-arranging nodes breaks the output...

Check out my dst (decorated syntax tree) library: it allows you to manipulate Go source without breaking the comments and line-feeds:

https://github.com/dave/dst

Reminds me of C# Code Analyzers based on the Roslyn compiler. It is a deal breaker for a language to have a compiler (in the same language) which exposes the intermediate phases and allow to participate in them.

A deal breaker? Seems that’s a good thing.

Lisp will blow your mind.

Smalltalk more so. :)

> Lisp will blow your mind.

If you're easy to impress and up until you have real world problem to solve.

I have used Lisp for 20 years, it's basically a fun toy, nothing more.

It's very hard to build anything production-hardened with it, nor anything really fast.

What is the percentage of games built in Lisp ?

What is the number of database back-end built in Lisp ?

How many embedded platform firmware written in Lisp ?

Lisp is an academic toy, fun to play with for sure, not something you want to turn to if your livelihood is involved - unless you're a fanatic.

"Game changer", perhaps?

True. I am a non native speaker picking sometimes the wrong idioms

Is this a Babel but for Go?

Reply on news.ycombinator.com