GHC.Core.Unify

tcMatchTy t1 t2 produces a substitution (over fvs(t1)) s such that s(t1) equals t2. The returned substitution might bind coercion variables, if the variable is an argument to a GADT constructor.

Precondition: typeKind ty1 eqType typeKind ty2

We don't pass in a set of "template variables" to be bound by the match, because tcMatchTy (and similar functions) are always used on top-level types, so we can bind any of the free variables of the LHS. See also Note [tcMatchTy vs tcMatchTyKi]

Like tcMatchTy, but allows the kinds of the types to differ, and thus matches them as well. See also Note [tcMatchTy vs tcMatchTyKi]

Like tcMatchTy but over a list of types. See also Note [tcMatchTy vs tcMatchTyKi]

Like tcMatchTyKi but over a list of types. See also Note [tcMatchTy vs tcMatchTyKi]

This is similar to tcMatchTy, but extends a substitution See also Note [tcMatchTy vs tcMatchTyKi]

Like tcMatchTys, but extending a substitution See also Note [tcMatchTy vs tcMatchTyKi]

Like tcMatchTyKis, but extending a substitution See also Note [tcMatchTy vs tcMatchTyKi]

This one is called from the expression matcher, which already has a MatchEnv in hand

Simple unification of two types; all type variables are bindable Precondition: the kinds are already equal

Like tcUnifyTys but also unifies the kinds

(tcUnifyTysFG bind_fam bind_tv tys1 tys2) does "fine-grain" unification of tys1 and tys2, under the control of bind_fam and bind_tv. This version requires that the kinds of the types are the same, if you unify left-to-right. See Note [The Core unifier]

Unify or match a type-family RHS with a type (possibly another type-family RHS) Precondition: kinds are the same

Some unification functions are parameterised by a BindTvFun, which says whether or not to allow a certain unification to take place. A BindTvFun takes the TyVar involved along with the Type it will potentially be bound to.

It is possible for the variable to actually be a coercion variable (Note [Matching coercion variables]), but only when one-way matching. In this case, the Type will be a CoercionTy.

BindFamFun is similiar to BindTvFun, but deals with a saturated type-family application. See Note [Apartness and type families].

Allow binding only for any variable in the set. Variables may be bound to any type. Used when doing simple matching; e.g. can we find a substitution

S = [a :-> t1, b :-> t2] such that
    S( Maybe (a, b->Int )  =   Maybe (Bool, Char -> Int)

Allow the binding of any variable to any type

Allow the binding of a type-family application to any type

See Note [Unification result]

Why are two types MaybeApart? MARInfinite takes precedence: This is used (only) in Note [Infinitary substitution in lookup] in GHC.Core.InstEnv It's really only MARInfinite that's interesting here.

Given a list of pairs of types, are any two members of a pair surely apart, even after arbitrary type function evaluation and substitution?

liftCoMatch is sort of inverse to liftCoSubst. In particular, if liftCoMatch vars ty co == Just s, then liftCoSubst s ty == co, where == there means that the result of liftCoSubst has the same type as the original co; but may be different under the hood. That is, it matches a type against a coercion of the same "shape", and returns a lifting substitution which could have been used to produce the given coercion from the given type. Note that this function is incomplete -- it might return Nothing when there does indeed exist a possible lifting context.

This function is incomplete in that it doesn't respect the equality in eqType. That is, it's possible that this will succeed for t1 and fail for t2, even when t1 eqType t2. That's because it depends on there being a very similar structure between the type and the coercion. This incompleteness shouldn't be all that surprising, especially because it depends on the structure of the coercion, which is a silly thing to do.

The lifting context produced doesn't have to be exacting in the roles of the mappings. This is because any use of the lifting context will also require a desired role. Thus, this algorithm prefers mapping to nominal coercions where it can do so.