chumsky

I decided to look; just found these: chumsky (parser combinator): https://github.com/zesterer/chumsky LALRPOP (LR(1)): https://github.com/lalrpop/lalrpop grmtools (YACC) https://github.com/softdevteam/grmtools/ re: Other parsers: https://softdevteam.github.io/grmtools/master/book/othertool... antlr4rust: https://github.com/rrevenantt/antlr4rust

I attempted to use this but was disheartened but the fact that it doesn't statically type node names. Tree Sitter doesn't either but it has much more of an excuse given that it targets C. https://github.com/lezer-parser/lezer/issues/8 The dev seems mildly hostile to outside involvement too, so I moved on. These days I use Chumsky which is Rust rather than Typescript, but also way more awesome, if you can deal with the often incomprehensible compilation errors at least! https://github.com/zesterer/chumsky

Chumsky still has trouble with left recursion, like many PEG parsers, but it's fairly easy to rewrite such grammars without left recursion as demonstrated in the tutorial: https://github.com/zesterer/chumsky/blob/master/tutorial.md

Tree-sitter appears to be ultra-focused on producing valid syntax trees really fast. This is great for e.g. syntax highlighting, but suboptimal in cases where you are writing a reference parser for your custom language and want to provide very useful error descriptions. Chumsky seems to be more suited for the latter (and also has a part of tutorial about precedence[0], so it seems to deal at least with that case). This overview of parser tradeoffs may be helpful: https://blog.jez.io/tree-sitter-limitations/. [0] https://github.com/zesterer/chumsky/blob/master/tutorial.md#...

It's mentioned in the performance section, "another crate with similar design". https://github.com/zesterer/chumsky#performance

I have some thoughts about this: https://github.com/zesterer/chumsky/issues/20#issuecomment-9... TL;DR: The best approach, in my view, is to detect whitespace in the lexer and emit fake delimiter tokens for the parser so that the parser-level syntax is still context-free.

Something to search through files, like "grep", but allowing combinational logic like "find" does. That would allow you to, for example, find files that contain "remote", and, "machine learning". Obviously this can be done with a little Python/Bash script, but a command line utility that supports this would be nice. I was going to write this utility myself, until the part where I had to implement the parsing of the combinational logic (since it can be arbitrarily nested/chained), and I didn't find tools in the language of my choice (Rust) back then to make that easy. I did find a rust library to do just that yesterday[0], so I myself might get on it! [0] https://github.com/zesterer/chumsky