许杰友 Jieyou Xu (Joe)
ec2cc761bc
[AUTO-GENERATED] Migrate ui tests from // to //@ directives
2024-02-16 20:02:50 +00:00
León Orell Valerian Liehr
02320b502d
Improve the diagnostics for unused generic parameters
2024-02-01 16:18:03 +01:00
León Orell Valerian Liehr
90d6fe2cba
Imply outlives-bounds on lazy type aliases
2023-12-28 02:03:43 +01:00
lcnr
11d16c4082
update use of feature flags
2023-12-14 15:22:37 +01:00
Nilstrieb
41e8d152dc
Show number in error message even for one error
...
Co-authored-by: Adrian <adrian.iosdev@gmail.com>
2023-11-24 19:15:52 +01:00
Esteban Küber
7411e25abe
Account for Weak alias kinds when adding more targetted obligation
2023-08-26 20:10:19 +00:00
León Orell Valerian Liehr
051eb7ca7c
Unlock trailing where-clauses for lazy type aliases
2023-08-10 16:13:08 +02:00
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
Michael Goulet
ba4a2f7cb7
Resolve target type of coercion
2023-08-07 19:06:18 +00:00
León Orell Valerian Liehr
5468336d6b
Store the laziness of type aliases in the DefKind
2023-08-07 15:54:31 +02:00
León Orell Valerian Liehr
263a0dec60
Compute variances for lazy type aliases
2023-08-03 01:38:23 +02:00
León Orell Valerian Liehr
0ca432844c
Check lazy type aliases for well-formedness
2023-07-30 11:24:15 +02:00
