participle

If you are wanting proper SQL command support, you could copy the SQLite parser approach. Properly parsing all valid command texts is not a problem that I would find compelling unless I was being compensated for it. https://www.sqlite.org/lemon.html You could probably use something like participle, but you'd have to translate the grammar. https://github.com/alecthomas/participle

I like the UX, but the results are full of content farms and weird ranking for the query "golang parser" (https://you.com/search?q=golang+parser). OTOH it is much faster than kagi. First result is good: pkg.go.dev/go/parser Second result looks like a content farm: golangdocs.com/golang-parser-package Third result looks like a valid Chinese search result, but it's a duplicate of the first result and also _very_ weird that it would rank that highly: golang.cm/pkg/go_parser.htm Then the next two results are content farms: golangexample.com/tag/parser/ golangexample.com/a-dead-simple-parser-package-for-go/ Then a valid result from a low-starred GH project: github.com/prataprc/goparsec Then a good result: blog.gopheracademy.com/advent-2014/parsers-lexers/ Then a random seemingly unrelated academic paper: www.arxiv.org/abs/1505.08075 Then a val

Couple of reasons. 1) Because I'm a fan of few dependencies and lex/yacc are non-Go dependencies. 2) I've never used them and it'd probably take me longer to learn them than hand-write a lexer and parser. 3) Writing a lexer is trivial, and writing a recursive-descent parser is fun and not that hard. As to the state of lexing/parsing in the Go world. There's a simple scanner (text/scanner) in the stdlib. I've run across this quite neat parser library that's based off structs and tags: https://github.com/alecthomas/participle ... but I really don't know the landscape very well.