

An AST-query language, so you can do arbitrary searches without having to code them up and restart the editor. a documentation-like view that lists a struct at the top, and functions taking a pointer to that struct after that, with only the functions folded by default. You can dream up lots of use cases here, e.g.

Many IDEs have a window showing all files, and, hierarchically, all top-level code elements inside them.When opening file_name:function, we don't really need to show the entirety of the file, just visualize that one function node.Since we're working with ASTs, we don't need to address code snippets by file_name:line_number anymore.
#LIGHTTABLE CODE FOLDING HOW TO#
I promise it's going to make some sort of sense by the end.Įssentially, I came up with a feature I didn't know I wanted until thinking about how to implement something like Stride for Go (that's a whole other can of worms I am not going to touch on today). That's a lot of time to spend thinking, so let me first apologize for the incoming wall of text. Thanks to the reddit hype around direct AST editing these past couple weeks, I've been thinking.
