rust-esp32-std-demo VS rust-analyzer

This is my link: https://github.com/ivmarkov/rust-esp32-std-demo

A complete STD demo on ESP32C3

I'm trying lots of Rust demos (including rust-esp32-std-demo, esp32-spooky-maze-game) for ESP32 on my M5GO kit with ili9342c controller and all of them struggle to give fullscreen (320x240) frame-rate > 5.

I used this demo as a guide, it uses esp-idf for rust, and allows you to use std

rust-esp32-std-demo works quite well with WiFi, HTTPS and MQTTS. The only thing I could not make work (but I did not put much effort into it) was using async primitives. That part seems to be experimental, indeed.

FWIW I've very recently gotten https://github.com/ivmarkov/rust-esp32-std-demo (which is a pretty comprehensive demo) running on a TinyPICO (w/ESP32) and am looking forward to building out my own projects next.

I'm using this template project to get started with the esp32, though I've started fresh in a new main function. Every time I build the project -even if I only add a blank line to main - it seems to re-compile bindgen and embuild, and regenerate the bindings for a variety of packages that have C components. I haven't made any changes to these though and the process takes a full 90 seconds. In addition nothing in the bindings that are getting generated shows up in intellisense in vscode. Any help appreciated.

This worked fairly well for me. I assume that's where the book takes you, bit I've missed if you said if you're trying to use std or no_std. https://github.com/ivmarkov/rust-esp32-std-demo

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