←back to thread

166 points ingve | 3 comments | | HN request time: 1.476s | source
1. mahirsaid ◴[] 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 #
2. estebank ◴[] No.44009626[source]
When maintaining a project, one gets exposed to the worst parts of it at an elevated rate. This makes maintainers be more critical than most, as we have an skewed view of the projects faults. So I can absolutely understand when someone claims that rustc has bad errors. I've seen them. But for most people most of the time the output is actually quite good. That shouldn't stop us from being better. I'm thankful for the OP because it does show that we do improve over time.

I keep saying that the most effective thing we can do to help someone learning the language is to tell them to try in 6 months (as we expect it'll be better then).

3. csomar ◴[] 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.