rust-for-rustaceans.com
nomicon
rust-for-rustaceans.com | nomicon | |
---|---|---|
7 | 87 | |
143 | 1,693 | |
- | 2.2% | |
6.1 | 5.6 | |
3 months ago | 26 days ago | |
CSS | CSS | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rust-for-rustaceans.com
-
Hardcore books
https://rust-for-rustaceans.com/ is meant to be a book for more advanced concepts.
-
How to Practice and Learn Rust for Production Level Code?
RustForRustaceans has great in depth explainations of most (all?) Rust concepts. So I would pick this one once you're familiar with the basic concepts explained in thee book.
-
Is there a good book/app I can learn rust from?
Another good piece, but I wouldn't say its for beginners, is Rust for Rustaceans by Jon Gjengset. Its definitely more intermediate topics than beginner. Still good to know about it ;)
-
Suggestions for reading
Rust for Rusraceans
-
Week 3 of learning rust - learning resources
For a deeper dive into the language and stdlib, the Crust of Rust videos are great. Also, Jon's book Rust for Rustaceans is a good continuation when you've finished the official book.
-
Rust vs Go
Rust for rustaceons includes a decent explanation of how the whole thing works.
-
Best book after the official Rust book?
I love this honest, high-level take on the book. So much so that I put it in "what readers say" on rust-for-rustaceans.com. Hope you don't mind!
nomicon
-
[Media] I'm comparing writing a double-linked list in C++ vs with Rust. The Rust implementation looks substantially more complex. Is this a bad example? (URL in the caption)
itโs even written by the same person that wrote the Nomicon (the guide to the dark arts of unsafe)
-
Rust books to read
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
-
Thread-shared boolean flag
Nonononono. SeqCst is the most error prone memory order: https://github.com/rust-lang/nomicon/issues/166
-
[Media] Hashmap behaviour inside a loop due to lifetime issue
Hope this helps. For more details, see the Rustonomicon. I referenced the subtyping chapter here extensively.
-
Unsafe Rust
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.
-
Stepping up the YAML engineer game
Have you got a moment to read through the good book , after reading through this perhaps try the Rustonomicon.
- Questions about ownership rule
-
CppCon 2022 Best Practices Every C++ Programmer Needs to Follow โ Oz Syed
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++.
-
How to write deserializer for custom binary protocol?
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.
-
Performance critical ML: How viable is Rust as an alternative to C++
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.
What are some alternatives?
rules_closure - Closure rules for Bazel
book - The Rust Programming Language
RustBooks - List of Rust books
mdBook - Create book from markdown files. Like Gitbook but implemented in Rust
vim-medieval - Evaluate Markdown code blocks within Vim
rust-ffmpeg - Safe FFmpeg wrapper.
wuffs - Wrangling Untrusted File Formats Safely
Theseus - Theseus is a modern OS written from scratch in Rust that explores ๐ข๐ง๐ญ๐ซ๐๐ฅ๐ข๐ง๐ ๐ฎ๐๐ฅ ๐๐๐ฌ๐ข๐ ๐ง: closing the semantic gap between compiler and hardware by maximally leveraging the power of language safety and affine types. Theseus aims to shift OS responsibilities like resource management into the compiler.
Exercism - website - The codebase for Exercism's website.
eslint-plugin-immutable - ESLint plugin to disable all mutation in JavaScript.
miri - An interpreter for Rust's mid-level intermediate representation