ts-rs VS rust-analyzer

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.

go build 3.62s user 0.76s system 171% cpu 2.545 total

I was looking forward to parallel front-end[4], but I have not seen any improvement for these small changes.

[1]: https://github.com/rust-lang/rust-analyzer

For example, intelephense can show diagnostics in real time, there is no need to save the file to get new diagnostics. But rust-analyzer, the language server for rust, can only update diagnostics after saving the file.

6. Rust Analyzer

The rust-analyzer readme suggests you go here for support request. But even there, you'll need to provide more details to get useful help.

For example: https://github.com/rust-lang/rust-analyzer/blob/master/docs/...

> If you create an LSP, it will work best in VS Code.

Any editor can work just as well as (or even better than) VS Code.

So, apparently the reason why rust-analyzer, the LSP server for Rust does not have persistent caching is because it would make "optimizing initial passes less important".

All I want to know is: Will it have a build configuration pulldown?

I am not a Rust dev. It surely looks great.

However, from what I understand it seems to supply just a parser separate from the Rust compiler (https://github.com/rust-lang/rust-analyzer/tree/master/crate...) trying to keep up with Rust‘s development. So, in principle, it could have been just another treesitter parser plugin, too.

So, again, the LSP framework does not directly provide any magical benefit over a static parsing framework. All the semantic analysis capabilities stem from a good parser.

rust-analyzer > manual > helix > binary > rustup component add rust-analyzer