TX-2-simulator VS chumsky

Source code

You could implement some opcodes at https://github.com/TX-2/TX-2-simulator

Thanks to /u/TGSCrust I've got things working now. In case anybody else is interested in this, I now have a complete working example.

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).

Here's an example of a tape loader program from a very fancy machine, the TX-2. The TX-2 was fancy in a lot of ways, but most relevantly here because the tape loader code was set up permanently on a plugboard instead of having to be toggled in at boot time. The TX-2 is interesting and important because it was the machine that Ivan Sutherland's Sketchpad ran on.

https://github.com/TX-2/TX-2-simulator is written in a combination of Rust and Typescript. It's not finished yet, and the UI needs lots of improvement.

https://github.com/TX-2/TX-2-simulator could really use some help

This github workflow builds this project and deploys it to the gh-pages branch of this project whose main branch isn't interesting.

If you're interested, please take a look at the TX-2 project's website and, if you like, the source code. If you haven't eaten in the last hour or so, you might also find it interesting to take a look at the online demo. There's a collection of "good first issue" items too.

TX-2 (code)

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

there’s also chumsky: https://github.com/zesterer/chumsky

We are using technique called parser combinator. And we are using a library chumsky to write parser combinators.

rust-langdev has a lot of libraries for building compilers in Rust. Perhaps you could use these to make your implementation easier, and revisit it later if you want to build things from scratch. I'd suggest logos for lexing, LALRPOP / chumsky for parsing, and rust-gc for garbage collection.

The examples that come with chumsky and the chumsky tutorial and guide all define their parsers using closures.

Parser: https://crates.io/crates/chumsky

chumsky's zero-copy rewrite has reached its first alpha release, and I have migrated my pep-508 parser to it, as suggested in my last announcement.

On my side, nom is still advancing well and a new major version is in preparation, with some interesting work a new GAT based design inspired from the awesome work on chumsky, that promises to bring great performance with complex error types. 2023 will be fun for parser libraries!

I am using chumsky because I like the API, but it doesn't support zero copy at the moment. Although efficiency is good to have, it is not my primary good. This will probably get supported once chumsky implements support for it (see upstream issue).

Checkout https://github.com/zesterer/chumsky or https://github.com/rust-bakery/nom