command-line-rust VS nomicon

You absolutely must write programs, preferably using tests to ensure you are creating correct and reproducible code. May I suggest starting with my book, Command-Line Rust (O'Reilly, 2022). All the code/data/tests are in https://github.com/kyclark/command-line-rust Note that there are branches showing how to use the 4.x version of clap (command-line argument parser) rather than the 2.33 that was current when the book was published.

I think the best way to start learning a programming language is to write lots of small programs that you probably already know. Rust is a perfect command-line language, so I think it makes sense to start by implementing simple programs like "head" and "grep." I also think one should always learn to write and run tests, so I present my GitHub repo of inputs and tests you might like to use to write 14 such standard Unix command-line utilities: https://github.com/kyclark/command-line-rust If you want guidance on the language, I wrote a book called Command-Line Rust (O'Reilly, 2022) that explains all this code. One caveat is that the "clap" (command-line argument parser) module was at 2.33 when I published but is now v4, so you should look at the appropriate branches for versions of the programs that use the "builder" and "derive" patterns for that module. Or just use any old command-line parser you like as there's no requirement to use "clap." Best of luck to you!

You must write programs in a language in order to learn it. I also firmly believe that learning how to write and run tests is critical to learning any language. I wrote Command-Line Rust (O'Reilly, 2022) for the beginner (in Rust, at least) and with a focus on writing and testing small programs from very simple "Hello, world!" and getting increasingly more complex. You can look at https://github.com/kyclark/command-line-rust for the code/inputs/tests. Best of luck!

Code for the above book

I'm the author of Command-Line Rust (O'Reilly, 2022), which I wrote to introduce the language slowly to beginners by writing and testing short, focused programs. You can look over the code/tests/data at https://github.com/kyclark/command-line-rust. Note that there are branches that show the same programs using a more recent version of the "clap" crate.

I wrote Command-Line Rust (O'Reilly, 2022) to guide beginners in the language. You are challenged to write small functions and programs using tests to verify that everything is correct. You can look over the code and tests at https://github.com/kyclark/command-line-rust. Best of luck in your journey!

Here are the example programs from my book, Command-Line Rust (O'Reilly, 2022), along with the input files and tests: https://github.com/kyclark/command-line-rust

I like to suggest that students write programs they already know (or at least understand). For instance, you probably understand that head shows the first few lines of a text file, and you probably can already implement some version of that in one or two languages you know. Try that in Rust. I wrote 14 BSD/GNU command-line utilities in Rust for learning purposes. I wouldn't consider these high-performance/production programs as they are tailored to learning the language. I also stress how to test programs, so there are tests and inputs you can use to verify your programs match the output of the original programs (or you can modify these to suit your own tastes for how you would like them to work). https://github.com/kyclark/command-line-rust

Here are some more examples you may or may not find useful: https://github.com/kyclark/command-line-rust I tend to have a main() that calls a library's run() function that returns a Result and then exit with a nonzero code and error message on a failure.

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.