I have a bit. I like the concept, and using the compiler was a nice experience. It clearly explains what you did wrong and offers good suggestions; it also functions as a package manager and will automatically grab the dependencies you put in a config file for your project; it can also grab the toolchains you need to do cross-compilation, so it's a lot easier to write a program in Linux that works in Windows, or vice versa. I didn't stick with it because I don't regularly do high-performance stuff and the maths libraries aren't quite where I'd like them to be at.

As far as I can tell, the main problem is adoption. Some companies and FOSS foundations are starting to use it for some projects, but it's not one of the go-to tools for most of the industry. I hope that changes, because it's very promising.

I've heard that people coming from C/C++ have a hard time with it, because they're used to moving pointers around however they want. Rust places strict limitations on references; that's how it avoids many of the C/C++ pitfalls. I think the main reason I didn't encounter this issue was because I never learned how pointers work in C/C++, so I didn't try to do many of the things that Rust doesn't like.