Rustlings VS rust-analyzer

The Rustlings exercises

Did you try the rustlings already?

Did you checkout rustlings I found it really fun to exercise

Start with Rustlings + reading through the Rust book

I’d recommend working through rustlings rather than watching videos for basic rust understanding: https://github.com/rust-lang/rustlings. It is essentially a set of quick exercises to get you familiar with the language and how to fix common build errors.

For advanced Rust “Jon Gjengset” has posted a number of long-form videos on YouTube that are very good. Search for it.

For code examples, find a crate in an area that you are interested in and clone the repo. There are so many to choose from that it would be unfair to single anything out. Variation is good, not bad. If you see lots of generics and macros then skip it for early learning purposes.

Instead of writing something from scratch I’d recommend rewriting something you are familiar with in but in Rust. For example, if you did advent of code (if that is your thing) in python then write it in Rust and find a repo of someone who solved the same problems in Rust.

The Rust book is excellent. https://doc.rust-lang.org/stable/book/

Hi Reddit, I'm a beginner on Rust and currently practicing on the Rustings project (https://github.com/rust-lang/rustlings)

-- all the opts to send to nvim-lspconfig -- these override the defaults set by rust-tools.nvim -- see https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#rust_analyzer server = { -- on_attach is a callback called when the language server attachs to the buffer -- on_attach = on_attach, settings = { -- to enable rust-analyzer settings visit: -- https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/user/generated_config.adoc ["rust-analyzer"] = { -- enable clippy on save checkOnSave = { command = "clippy" }, } } },

I'm having the exact same issue as here where using async fn causes an error

Correct me if I'm wrong, but format_args_capture still isn't supported yet. https://github.com/rust-analyzer/rust-analyzer/issues/11260

I often run into this issue, and the only way to solve it right now is to reload the entire VSCode window.

- cargo clippy will point out lots of other nice things you could do probably! If you use VS Code be sure to get https://github.com/rust-analyzer/rust-analyzer and be sure to configure it to run cargo clippy on save, super useful way to get immediate feedback on the code.

In this sense, I am very against having things like types which split stuff across linguistic category, rather than a slice of the domain. I think it’s much better to have, eg, types module in the http_api crate, and a separate types module in the persistsnce crate with somewhat duplicate definitions and explicit conversion between the two. I am a huge fan of writing tons of adaptor boilerplate like here: https://github.com/rust-analyzer/rust-analyzer/blob/master/crates/rust-analyzer/src/to_proto.rs.

We started with a similar setup in rust-analyzer: obviously, when you want to convert X to Y, you need a trait for that, right? But then I’ve refactored that to just a bunch of functions in https://github.com/rust-analyzer/rust-analyzer/pull/4418, and never looked back. In ra case, that was a case of concrete abstraction (https://matklad.github.io/2020/08/15/concrete-abstraction.html) — all the callers wanted to convert specific X to specific Y, no one was using the trait generically.

Seems so, and looks like there aren't any issues open for either case yet. Would you like to do the honors? https://github.com/rust-analyzer/rust-analyzer/issues

You can either use rust-analyzer[1] (for which vscode is most well supported), or IntelliJ Rust [2]. Personally, I use `rust-analyzer` with vscode as a bevy developer.

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