Hi everyone!
I am the author of marser [1], a parser-combinator library for rust.
This tool can be used to see what the marser code of a certain grammar could look like, to help users explore how to use marser.
Feel free to ask me any questions or suggest improvements!
The main aim of the library is to make parsers readable and understandable by enabling users to write code that resembles formal grammars / ebnf (more on that in the blog post).
It also has additional features like error recovery, custom error diagnostics and a TUI for debugging the parsers.
This is my first library, so I would really appreciate some feedback on design decisions / usability etc.
Disclaimer: I have used AI for parts of the documentation, for some of the macro code and things like the TUI viewer but the core parsing code has been written by me.
I remember being able to have unlimited Claude opus queries on the free student plan, they must have had to change something to not loose too much koney
I think there are costs beyond having to sacrifice writing code yourself.
When prototyping yourself you learn a lot about the problem, see what design decisions lead to what tradeofs.
While you write code your brain is always running in the background, giving you thoughts about how things could break, where the structure could be simplified, where the code could be extended.
I feel this is lost or at least reduced a lot when an LLM writes code because you have a lot less contact with the software.