Exercism - website VS nomicon

First to get a grasp of language use [Exercism(https://exercism.org/) anything similar. You can also practice leetcode questions in language of your choice. Leetcode may not help you with day to day stuff but it will force you out of your comfort zone and will make you think about what and how to write.

Here's a better way to learn at Javascript.info. Sprinkle in some online tutes such as Brad Traversy videos, build some mini-projects, and perhaps a coding challenge site such as edabit or exorcism.

All the exercises on https://exercism.org/ have been given a fresh coat of paint, removing their looped JSON test cases in favor of cases written fully in Raku.

https://exercism.org/ is my go-to spot when learning a new language to get lots of exercise. Just see how far you can progress.

Check out https://exercism.org/

Exercism

If you like to do exercises, I can recommend the website https://exercism.org It has al kinds of exercises and mentoring.

If you want improve your coding skills. Try https://exercism.org. They have tracks for all types of languages, including C.

exercism.org if you want to learn basics of some concepts or languages, I use it to learn other languages than the main one I work with. It's really nice IMO.

it’s even written by the same person that wrote the Nomicon (the guide to the dark arts of unsafe)

If you want to dive deeper you can always have other options but now there are concrete cases, if you want to do low level thing https://doc.rust-lang.org/nomicon/ while if you want multi thread/concurrency stuff https://marabos.nl/atomics/ . There are many many books so you will have to point yourself to what you want

Nonononono. SeqCst is the most error prone memory order: https://github.com/rust-lang/nomicon/issues/166

Hope this helps. For more details, see the Rustonomicon. I referenced the subtyping chapter here extensively.

Nice video! Glad I could help out. This stuff is hard, and I'm still learning a lot about it myself even years later. The Rustonomicon is a great read if you haven't already.

Have you got a moment to read through the good book , after reading through this perhaps try the Rustonomicon.

That is not what UB means. Undefined Behaviour is behaviour that the compiler is allowed to assume will never happen, and which can consequently cause miscompilations due to optimisation passes gone wrong if it does in fact occur in the source code.

It's true that Rust does not have a written specification that clearly delineates what is and isn't UB in a single place. But:

1. UB is impossible in safe code (modulo bugs in unsafe code)

2. There are resources such as the Rustinomicon (https://doc.rust-lang.org/nomicon/) that provide a detailed guide on what is and isn't allowed in unsafe code.

In practice, it's much easier to avoid UB in Rust than it is in C++.

However, this is a wide topic out of scope for a Reddit comment, so maybe just read the Rustonomicon. It explains everything about data handling in Rust.

The ownership model & borrow checker makes rust a bit of an awkward language in which to write complex data structures like trees and graphs. It can be done - since you can always use raw pointers & unsafe code when you absolutely need to to treat rust like C. But the language fights you, and the community can get a bit moralistic about this sort of thing. The rust nomicon is a fantastic resource for learning the limits of the borrow checker, and where and how to use unsafe code correctly. You will need unsafe less than you think you will, but sometimes you will have no choice.