Have you erased the continuation of the message that is saying something about "similar names, but are actually two distinct types"?
It is a common error if you have two dependecies that export the same third dependency and your code makes an assumption that the versions of the third dep match.
All other languages either straight-up don't support multiple versions of the same dep, or throw random errors at runtime. So this message is a consequence of rust supporting things that other langs only dream of.
Rust's compiler is more picky than most, but is really impressive in how it explains the errors and advises on how to fix them. It's a really good feature of Rust.
::: spoiler Expansion dropdowns are nice.
They make it easier to fit in many errors in a small widget
and provide the user the option to see the rest of the error right there.
Then you have the option in the context menu to go to the actual error text.
I expect these things to be basically available in my IDE
:::
Have you erased the continuation of the message that is saying something about "similar names, but are actually two distinct types"?
It is a common error if you have two dependecies that export the same third dependency and your code makes an assumption that the versions of the third dep match.
All other languages either straight-up don't support multiple versions of the same dep, or throw random errors at runtime. So this message is a consequence of rust supporting things that other langs only dream of.
I enjoyed the joke but yeah I thought Rust was known for quite good error messages in general. I haven't used it though myself.
Rust's compiler is more picky than most, but is really impressive in how it explains the errors and advises on how to fix them. It's a really good feature of Rust.
The problem is ides inlining only part of the error and generally skip all the helpful text on how to fix the error.
::: spoiler Expansion dropdowns are nice. They make it easier to fit in many errors in a small widget
and provide the user the option to see the rest of the error right there.
Then you have the option in the context menu to go to the actual error text.
I expect these things to be basically available in my IDE :::
Yeah, C++ would give a linker error.
But that won't be C++, but the linker.
Because as far as C++ goes, all stuff is in a single source file, until fairly recently.
.map_err(utils::err_magic_dont_look)That was how I solved it ;)