Is that because async is involved? I have minimal experience with async Rust code, but my experience with Rust compiler errors has been superb so far. The compiler always tells me exactly where things went wrong and the error messages are quite informative.
Re:Rust's 2018 roadmap
by steveklabnik on Tuesday March 13, 2018 @03:13AM
(#16574321)
Yes, but also no. That is, async is done via futures, which means that you're composing a lot of futures together, which means that you have a long type signature, which means that if you get a type mismatch, you get quite a long error, where 99% of the type is the same.
This is indeed very frustrating. I've had to learn to translate between "what the compiler is telling me" and "what the issue actually is".