Usually, you don't start learning a new language with multithreaded operations..
In that sense, adding a gc to rust for single threaded programming, is almost useless : it's not helping that much and you're not learning.
In that sense, adding a gc to rust for single threaded programming, is almost useless : it's not helping that much and you're not learning.
When I have started with rust I was not writing stuff with Box/Rc/Arc... or even explicit lifetimes. Not saying that I was cloning everything but for simple stuff you can come long way with just moving and simple borrowing.
For an already experienced programmer, it's hard not to think about using multiple threads, even when just starting in the language. I know my few first Rust programs were using multithreaded constructs and I found that especially easy to do safely in Rust (when I started, there was already crossbeam and rayon, both making a lot of things easier).
Why not? I mean, maybe not your first ever programming language, but - why should you not get used to doling out work to all available threads to begin with?
If you don't or are unsure about that, then stick to simpler forms of programming or use type-hinted Python instead.
This would the recommendation I would make to anyone asking me that question !