bevy-cheatbook VS rust-analyzer

You can see working examples of nearly everything you asked about in the Bevy Cheatbook

The biggest source of wasted time for me was finding out that my shaders which were working on native didn’t work on webgl. For one of the more perplexing error messages, I opened this issue in the cheatbook a while ago.

wasm mostly works :) There's a nice PR open on the cheatbook that documents the process quite well that you can work off of.

Great! Are you okay if I submit this to the Unofficial Bevy Cheatbook? This question comes up pretty frequently and this is a great little snippet.

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.

You may file issue at github rust-analyzer

I've contributed to rust-analyzer and nushell and had a great experience in both! Tons of open issues with a huge range of difficulties, and the maintainers are really helpful in providing hints to get started.

For something more concrete you can try and ask around on their zulip or browse their issues.

More info here: https://rust-analyzer.github.io/ and here: https://rust-analyzer.github.io/manual.html#installation

You can submit feature requests in the repository: https://github.com/rust-lang/rust-analyzer/

sh git clone https://github.com/rust-lang/rust-analyzer.git && cd rust-analyzer cargo xtask install --server

Thanks for the ideas! Separating out presentation crate into it's own crate sounds like a great idea. Re "temporarily stopping rust-analyzer", I came across this trick[0] to make RA use a different build path (trading off disk-space for speed, but I mean, disk space is cheap).

Re: cranelift, I gotta check that out! Thanks for the reminder!

[0] https://github.com/rust-lang/rust-analyzer/issues/6007#issue...

I also filled a new rust-analyzer issue for the cases that remain broken here.

Arc (or Rc if single threaded) sounds like a good fit since you mention immutability and no parent-pointers. If the lack of parent pointers or contextual information gets frustrating, I just want to mention the "Red/Green trees" approach used by Roslyn and rust-analyzer (link) where the "green tree" stores the data using basic Arcs and child pointers only, but later on you can create a "red tree" rooted at any green node which provides parent pointers as you navigate through the tree.