ouch VS pest

There's one that's also written in rust: https://github.com/ouch-org/ouch

I use for some time Ouch, It's a CLI tool for compressing and decompressing various formats (at this moment .tar, .zip, .gz, .xz, .lzma, .bz, .bz2, .lz4, .sz, .zst). You can compress, decompress or list archive. It's just one binary application, without dependencies and for my usage is very fast. I don't create a lot of archives, I usually unpack them when I download something from the web and so far I'm very happy with ouch. It has a simple command syntax. I use on my machines with Debian musl version from release page and on Arch there are packages in AUR (to build with cargo or binary version).

I personally use ouch. It suppirts a bunch of stuff and to quote the readme:

ouch - a command-line app to unify file compression and decompression

Shameless plug here, my favorite project currently is ouch, nobody knows about it, but I think it might gain some traction when we publish it again.

And some related parser tools: - https://github.com/kevinmehall/rust-peg - https://github.com/pest-parser/pest - https://github.com/lalrpop/lalrpop

I had recently completed the first year of my Computer Science class at school and will begin my second year soon. My schools' class forces the use of Java programming language, and I absolutely hated it. So, over the course of a little less than a month, I wrote my own programming language, in Rust (objectively best programming language), using pest, to be as similar to Rust as possible, but compiling to Java.

I second pest.rs. Using it is fairly intuitive and there's also a live playground on their website which is great for quickly developing and testing your AST (abstract syntax tree) parser for whatever language you're implementing.

This is where you'll run into trouble. People who write parsing-related Rust crates generally write things like pest that expect their syntax to be defined completely at compile time so the parser can be run through the compiler's optimizers for best performance.

Give https://pest.rs a try.

For now I have used pest to generate an AST that borrows from the given input. But if I can manage to make the parser generic over the return type it may be worth a refactoring.