diff options
| author | Chayim Refael Friedman <chayimfr@gmail.com> | 2025-08-28 03:35:22 +0300 |
|---|---|---|
| committer | Chayim Refael Friedman <chayimfr@gmail.com> | 2025-09-10 00:53:15 +0300 |
| commit | 1acb4c2c1621578ea787afb698ed8718cbdf3d4f (patch) | |
| tree | 80de0ff7f2bfdb93e9b034e7ac46401306b85656 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 0cce47c05bea6ac7748c46dfe2a5b1a64fe72cd6 (diff) | |
| download | rust-1acb4c2c1621578ea787afb698ed8718cbdf3d4f.tar.gz rust-1acb4c2c1621578ea787afb698ed8718cbdf3d4f.zip | |
An associated type is not a projection!
More correctly, a `TyKind::AssociatedType` is not the same as `TyKind::Projection`. We used to map next-solver `TyKind::Alias` to Chalk's `TyKind::AssociatedType`. This is very incorrect, as `AssociatedType` is assumed to be fully normalized, and caused a lot of type mismatches. Unfortunately fixing this causes a lot of stack overflows, because the next solver doesn't have something akin to `AssociatedType` so we normalize again and again. The reason is that is the lazy-normalization nature of the next solver, which means we need to stop normalizing everything. This will be fixed in the next commit.
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions