ts-rs VS nom

I agree, and disagree.

I agree that it limits the usage of the tool in a polygot environment. I disagree it's a downside.

The absence of an intermediary language does give some benefits to the first class citizen (in this case, Typescript).

However, there are some other developments [1] which attempt to make the Typescript type system an IDL to allow for better interop.

[1] https://github.com/Aleph-Alpha/ts-rs

Not the person you asked, but I’ve seen people use https://github.com/Aleph-Alpha/ts-rs to generate TS interfaces at compile time for use on the frontend. Saves a bunch of time when scaffolding up a new data model without having to use a custom gRPC plugin or something wonky like that. That makes Rust and TS a pretty powerful pairing IMO.

[Link]

Does anyone know how mature ts-rust is? I'm trying to use this with complex types (nested enums etc) and am running into some pain-points, especially when I have types defined across multiple files. Not sure if this is a legitimate limitation, or whether there's just more for me to do in terms of configuration etc.

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