-
I would put the book aside for a while and try some other approaches. You don't say what your other programming experience is, but you could go through the Rustlings. If you have some programming experience, try rewriting small programs in languages you know well, but in Rust. When you have problems, ask questions here or on one of the Rust Slack or Discord channels. Many Rustaceans are pretty generous with their time.
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
Just to clarify: You mean this one https://doc.rust-lang.org/book/ , right? Because 4.3 should be about Slices, not about fixing ownership errors. (Although in the chapter itself they might fix a few errors).
-
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.
-
There's also Easy Rust, an effort in translating the Rust Book into Simple English (limited vocabulary, limited use of idioms), which has now become a Book.