mirror of
https://github.com/rust-lang/rust-analyzer.git
synced 2025-10-01 22:31:43 +00:00
Introduce our own Chalk TypeFamily, instead of using ChalkIr
It's not very different, except we can directly use Salsa IDs instead of casting them. This means we need to refactor the handling of errors to get rid of UNKNOWN_TRAIT though.
This commit is contained in:
parent
6b5efe5bda
commit
4053fcfca0
4 changed files with 126 additions and 87 deletions
|
@ -291,7 +291,7 @@ impl FnTrait {
|
|||
}
|
||||
}
|
||||
|
||||
#[derive(Debug, Clone, PartialEq, Eq, Hash)]
|
||||
#[derive(Debug, Clone, Copy, PartialEq, Eq, Hash)]
|
||||
pub struct ClosureFnTraitImplData {
|
||||
def: DefWithBodyId,
|
||||
expr: ExprId,
|
||||
|
@ -300,7 +300,7 @@ pub struct ClosureFnTraitImplData {
|
|||
|
||||
/// An impl. Usually this comes from an impl block, but some built-in types get
|
||||
/// synthetic impls.
|
||||
#[derive(Debug, Clone, PartialEq, Eq, Hash)]
|
||||
#[derive(Debug, Clone, Copy, PartialEq, Eq, Hash)]
|
||||
pub enum Impl {
|
||||
/// A normal impl from an impl block.
|
||||
ImplBlock(ImplId),
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue