TX-2-simulator VS rust-analyzer

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)

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