build failure: librustc-0d83f02f-0.10-pre.so: undefined reference to `LLVMRustDebugMetadataVersion' #11880
Comments
|
Additional information - the latest commit - top of tree: Found commit related to LLVM: Thanks |
|
Can you provide a paste of the full session? The |
|
Sure, here it is ()on another machine I'll try to do make clean && make |
|
Ah, I just had the same problem crop up. This just needs a |
|
Thanks. |
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Feb 26, 2024
[`implied_bounds_in_impls`]: avoid linting on overlapping associated tys Fixes rust-lang#11880 Before this change, we were simply ignoring associated types (except for suggestion purposes), because of an incorrect assumption (see the comment that I also removed). For something like ```rs trait X { type T; } trait Y: X { type T; } // Can't constrain `X::T` through `Y` fn f() -> impl X<T = i32> + Y<T = u32> { ... } ``` We now avoid linting if the implied bound (`X<T = i32>`) "names" associated types that also exists in the implying trait (`trait Y`). Here that would be the case. But if we only wrote `impl X + Y<T = u32>` then that's ok because `X::T` was never constrained in the first place. I haven't really thought about how this interacts with GATs, but I think it's fine. Fine as in, it might create false negatives, but hopefully no false positives. (The diff is slightly annoying because of formatting things. Really the only thing that changed in the if chain is extracting the `implied_by_def_id` which is needed for getting associated types from the trait, and of course actually checking for overlap) cc `@Jarcho` ? idk if you want to review this or not. I assume you looked into this code a bit to find this bug. changelog: [`implied_bounds_in_impls`]: avoid linting when associated type from supertrait can't be constrained through the implying trait bound
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello. Just stumbled upon build failure.
Thanks
The text was updated successfully, but these errors were encountered: