To answer to your question, I will say it will take you time to understand and to be productive with Rust.
But, please stop, Go and Rust can't be compared, they don't have the same goal in mind.
Nonsense. For _certain things_ they can't be compared, but many things they can be. If I can compare Python and Rust, why can't I compare Go and Rust?
For example, I chose Rust at work recently for a project that was previously written in Go. How do you think I made that decision if I can't compare them?
Fundamentally yes, they're different languages. But seeing as Rust is quite usable in many areas it's perfectly valid to compare them. I see this "they can't be compared" so frequently that it's comical to me. Not trying to be insulting here, it's just perplexing.
I think it must stem from back in the day when Go was "incorrectly" labeled as a Systems Language. People ended up thinking that Rust and Go were competing for the same space. That there was bound to be a winner and a loser. They can happily co-exist, they're not at war, but they can and will frequently be compared. They have a ton of overlap.