tao VS chumsky

That sounds quite similar to Tauri’s Tao, so a brief comparison could come in handy.

Now the string Alt+Enter pressed! should be logged into the console every time I press Alt+Enter. But it doesn't work and I didn't know why ... until I found this open issue on the tao repository: https://github.com/tauri-apps/tao/issues/307

This crate is the backend for another project of mine, which is currently Windows only - it will be Linux compatible as well pending the closure of this issue on an upstream project. Should work on OSX as well in theory, but I have no way to test that at this time

Big fan of .mdx resources and GoldenDict. Unfortunately Wikit Desktop does not run on Wayland natively due to https://github.com/tauri-apps/tao/issues/248. Can Wikit disable global shortcuts to work it around?

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