Rustlings VS rust-analyzer

So here's the story. I decided to learn Rust, read the docs, solved the rustlings challenges. The next step in learning a new programming language is to build something with it. And so began my dilemma.

I'm learning Rust and solving the rustlings exercises.

Rustlings is a CLI-based open source project of small challenges that help to grow your knowledge of the language.

i can't truly speak to the relative steepness, i think like both rust and c++ can get quite steep depending on what you're doing but can also be simple in other cases. best to just try it out i'd say :) the rustlings guide https://github.com/rust-lang/rustlings which parallels the rust book https://doc.rust-lang.org/book/ is a good way to learn. doing things like advent of code could also help. the most common hurdles with rust are "lifetimes" and "the borrow checker", and it just takes practice to figure them out

I recommend checking out the Rustlings exercises - they provide a really good overview of approaching concepts in Rust, if you're having difficulty with the docs.

perfect thank you so much for the explanation and for the link i got it working :)

Working through the rustlings exercises

The book is great and was my original introduction to the language, but rustlings or Rust By Example might be more interesting for an interactive (and more self paced) approach.

Rustlings: This is a great resource for getting started with Rust, with small exercises to help you get comfortable reading and writing code.

You are correct actually, there was a bug that made us not accept the old configs in most cases, https://github.com/rust-lang/rust-analyzer/pull/13980. The next release should accept them again.

Please write in the comments if you know of any language servers I should test it with. Currently I tested only metals and rust-analyzer.

Most editors (or plugins for them) that support a LSP, like rust analyzer[0], can do it. This includes afaik (neo)vim (via coc.nvim), vscode (via rust-analyzer extension), emacs and Clion.

[0]: https://rust-analyzer.github.io/

fwiw, rust-analyzer cannot make use of this env var signaling a proc-macro that it is being expanded for completions currently (and is unlikely to be able to in the future) due to architecture reasons, https://github.com/rust-lang/rust-analyzer/issues/13731

That last bit of plumbing probably isn’t done yet, but https://github.com/rust-lang/rust-analyzer/pull/8955 would be the right base for that.

They announced about three weeks ago that rust-analyzer on OpenVSX is now published properly. (This was the bug for it.)

Hiya, that was my doing :) I added a media query so that rust. is white in dark mode and black in light mode. This way, rust. is visible in the README regardless of theme. I assume that your browser is displaying the SVG with a white background even in dark mode, which of course makes rust. disappear.

In the VS Code extension and on the website (https://rust-analyzer.github.io/), at least.

Not related. We just got https://github.com/rust-lang/rust-analyzer/pull/13588/ and thought a wider discussion might be beneficial.