rust/tests/ui/lazy-type-alias
Matthias Krüger 418b91a3d7
Rollup merge of #114594 - compiler-errors:new-solver-resolve-aliases, r=lcnr
Structurally normalize weak and inherent in new solver

It seems pretty obvious to me that we should be normalizing weak and inherent aliases too, since they can always be normalized. This PR still leaves open the question of what to do with opaques, though 💀

**Also**, we need to structurally resolve the target of a coercion, for the UI test to work.

r? `@lcnr`
2023-08-08 03:30:56 +02:00
..
auxiliary Store the laziness of type aliases in the DefKind 2023-08-07 15:54:31 +02:00
coerce-behind-lazy.current.stderr Resolve target type of coercion 2023-08-07 19:06:18 +00:00
coerce-behind-lazy.next.stderr Resolve target type of coercion 2023-08-07 19:06:18 +00:00
coerce-behind-lazy.rs Resolve target type of coercion 2023-08-07 19:06:18 +00:00
enum-variant.rs
enum-variant.stderr
extern-crate-has-eager-type-aliases.rs Store the laziness of type aliases in the DefKind 2023-08-07 15:54:31 +02:00
extern-crate-has-lazy-type-aliases.locally_eager.stderr Store the laziness of type aliases in the DefKind 2023-08-07 15:54:31 +02:00
extern-crate-has-lazy-type-aliases.locally_lazy.stderr Store the laziness of type aliases in the DefKind 2023-08-07 15:54:31 +02:00
extern-crate-has-lazy-type-aliases.rs Store the laziness of type aliases in the DefKind 2023-08-07 15:54:31 +02:00
type-alias-bounds-are-enforced.rs
unsatisfied-bounds-type-alias-body.rs
unsatisfied-bounds-type-alias-body.stderr
variance.rs