Chayim Refael Friedman 6bcfbbe8f9 Remove SolverDefId::ForeignId ...

Replace it with normal `SolverDefId::TypeAliasId`.

The split caused a very funny bug where code was getting `TypeAliasId` where it expected `ForeignId`, because `TypeAliasId` had a `From` impl from `hir_def::TypeAliasId` and `ForeignId` had not, plus a careless `into()`.

I could've fixed this specific bug but opted to remove the split instead; currently, it just provides more room for bugs, as we don't have typed IDs for the solver anyway, and even when we'll have (hopefully), that doesn't seem like a very useful distinction, for example in hir-def foreign types are just `TypeAliasId` with some flags.

Constructing a test for this isn't trivial; the trivial test (creating a foreign type, even proving a trait bound for it) fails to fail before the change, probably because we don't use the new solver everywhere yet so we don't trigger this specific code path.

2025-08-26 19:33:46 +03:00

..

src

Remove SolverDefId::ForeignId

2025-08-26 19:33:46 +03:00

Cargo.toml

Implement next trait solver

2025-08-09 16:08:58 +00:00