←back to thread

Evolution of Rust Compiler Errors

(kobzol.github.io)
166 points ingve | 1 comments | 16 May 25 13:22 UTC | HN request time: 0.206s | source
Show context
mahirsaid ◴[16 May 25 20:06 UTC] No.44009334[source]▶
Interesting enough i still hear people say the error messages from rust is confusing and none informative. I wouldn't say that i am proficient in Rust but i know enough about it and it;s tooling to distinguish the difference between different (LV " Low Level " ) languages. When you get a grasp of the Rust lang then you will know how helpful the compiler is in Rust compared to other languages. Highlighting the progress of the Rust lang compiler messages in this post really Depicts the refinement of their ( Rust lang team ) compiler messages.
replies(2): >>44009626 #>>44015506 #
1. csomar ◴[17 May 25 16:47 UTC] No.44015506[source]▶
When you have complex types with complex bounds, the compiler rarely can link these types/bounds and you end up with cryptic error messages. You know there is a missing bound somewhere but it could be anything until you read and fully understand the type structure that the author of the library has put. Sometimes there is a trait to import but the LSP sometimes catches it and in some odd cases does not. Shit really hits the fan if you are using proc-macros.