If your aim is to get proficient at Rust, specifically, it's probably best to not go down the inheritance rabbit-hole too far: Rust has essentially no inheritance mechanism, and one of the largest stumbling blocks for programmers coming from other languages is that they try to use inheritance-based designs, which don't really work in Rust.
On your broader point, I mostly agree. I believe that Rust can be a good first language for some people, but it's certainly not for everyone. Rust "helps" you to write quality software in part by requiring you to deal with lots of little details up front; this can be extremely instructive, but also deeply frustrating.
A language like Python, on the other hand, will let you ignore many of these details, which makes it easier to get programs that mostly work up and running. And in many situations, those extra details don't end up mattering at all. Sometimes, however, they do, and you'll unexpectedly encounter some weird behavior that can be difficult to diagnose.
Rust's learning curve is like scaling a cliff followed by pretty smooth terrain once you get past the initial difficulty, whereas a language like Python's is more like climbing a rocky hillside all the way up-- It's difficult to say which one is harder overall, but they're qualitatively different experiences.
I think I should've said "Classes" not inheritance necessarily.
My main point was to, for example, understand why my_class.my_method() works, how self is passed on implicitly for methods (I think one can even map setters and getters), and not for static methods etc.
Note that a struct is instantiated just like a class, and has methods, this is similarity that will be helpful.
A trait itself is on the surface similar to inheriting in my view, even the search for a .method up the ladder has a similar "preference" to inherent method vs trait method.
But yes, I did not mean a lot of detail about inheritance, but comfortably handle classes is useful imho.
It's true that if one comes to find inheritance, it simply isn't there !
I think that pratice is your best friend to learn
I start by trying to code some simple stuff in rust. Each time, I learn a new think and I want to test more.
It depends on one's personal skills on programming.
I found the "Project Euler" some time ago.
I think that most of the first 100 problems can be solved in Rust with a relatively basic knowledge in this language.
A good knowledge in algorithmic is also an advantage.
Nitpick: Rust error messages are extremely clean and helpful… if you know Rust!
It's not uncommon, for a beginner, to try to “explore a bit”… and stumble upon extremely deep rabbit hole with HRBTs, GATs and bazillion other things that compiler would happily bring into error messages… with you having no clue about what these all even are.
