mirror of
https://github.com/rust-lang/rust.git
synced 2025-05-14 02:49:40 +00:00
6fc0273b5a
Add `implement_via_object` to `rustc_deny_explicit_impl` to control object candidate assembly
Some built-in traits are special, since they are used to prove facts about the program that are important for later phases of compilation such as codegen and CTFE. For example, the `Unsize` trait is used to assert to the compiler that we are able to unsize a type into another type. It doesn't have any methods because it doesn't actually *instruct* the compiler how to do this unsizing, but this is later used (alongside an exhaustive match of combinations of unsizeable types) during codegen to generate unsize coercion code.
Due to this, these built-in traits are incompatible with the type erasure provided by object types. For example, the existence of `dyn Unsize<T>` does not mean that the compiler is able to unsize `Box<dyn Unsize<T>>` into `Box<T>`, since `Unsize` is a *witness* to the fact that a type can be unsized, and it doesn't actually encode that unsizing operation in its vtable as mentioned above.
The old trait solver gets around this fact by having complex control flow that never considers object bounds for certain built-in traits:
|
||
|---|---|---|
| .. | ||
| astconv | ||
| check | ||
| coherence | ||
| collect | ||
| impl_wf_check | ||
| outlives | ||
| structured_errors | ||
| variance | ||
| autoderef.rs | ||
| bounds.rs | ||
| check_unused.rs | ||
| collect.rs | ||
| constrained_generic_params.rs | ||
| errors.rs | ||
| hir_wf_check.rs | ||
| impl_wf_check.rs | ||
| lib.rs | ||
| structured_errors.rs | ||