AdventOfCode2021 VS nom

Re it turning into an infinite loop: Are you sure it was the reduction? Because I ran into the problem of recursing too deep in the explosion/splitting step when I tried disabling intermediate reductions. But it should not result in any nonbinary trees as intermediaries since all operations should retain this "binarity" which we start with. Which input made these problems for you? Then I can check my intermediaries for it (or you can check it via my code here https://github.com/SV-97/AdventOfCode2021/blob/main/Day_18_2/main.py)

Loved today's puzzle after I didn't really enjoy yesterday's at all. Solved it in Python and finally installed Python 3.10 for it - gotta say that Python is slowly becoming okay for language implementation stuff :D https://github.com/SV-97/AdventOfCode2021/blob/main/Day_16_2/main.py

Part 1: https://github.com/SV-97/AdventOfCode2021/blob/main/Day_04_1/main.py

Just in case you are not familiar with nom, it is a parser combinator written in Rust. The most basic thing you can do with it is import one of its parsing functions, give it some byte or string input and then get a Result as output with the parsed value and the rest of the input or an error if the parser failed. tag for example is used to recognize literal character/byte sequences.

I may be the only one not familiar, but nom refers to https://github.com/rust-bakery/nom which looks like a pretty handy way to parse binary data in Rust.

Lots of people use nom for their parsing needs, but that's not the only game in town and there other options.

As much as I love nom as well as other parser combinator libraries, regex-based parsers, BNF/EBNF-based parsers, etc. I always end up going back to plain old text-based char-by-char scanners.

I am using nom / nom_locate to build the parser side because I've done a handful of other projects with it, and I plan to use tower-lsp to hook up the language server side.

Look into a parsing library such as https://github.com/rust-bakery/nom

If we were in /r/learnrust I'd have recommended the nom crate for this.

Thanks to the flexibility of [nom](https://github.com/rust-bakery/nom), it is very easy to write your own parser in rust, read [this article](https://github.com/metaworm/luac-parser-rs/wiki/Write-custom-luac-parser) to learn how to write a luac parser

I've been working on an assembler and right now it uses nom. While nom isn't great for error messages, good error messages will be important for this particular assembler (current code), so I've been attempting to use the methods described by Eyal Kalderon in Error recovery with parser combinators (using nom).