Re:Uninitialized memory: Unsafe Rust is too hard
by masonium on Sunday January 30, 2022 @12:01PM
(#30138808)
I've seen this error a lot when working with two different versions of the same library. Specifically, you can directly include version A, but a different library depends on a version B, with some of that exposed in the public API.
Re:Uninitialized memory: Unsafe Rust is too hard
by staticassertion on Sunday January 30, 2022 @12:34PM
(#30139133)
I think the compiler will now give you a hint that they may be from different versions. If not, next time you see it you should open up a bug in rustc.
To anyone who gets a cryptic error message - that's a bug, report it.
Re:Uninitialized memory: Unsafe Rust is too hard
by eminence32 on Sunday January 30, 2022 @10:38PM
(#30144179)
Yup, newer compilers will give you an explicit hint about thee types from being different versions of different crates, but older compilers did not.
Does Rust actually give an error like `expected type Foo, but found type Foo`, as in both types are the same in the error? I don't think I've seen that before, but I don't write much Rust.
If both types are the same, what does the error mean?