ayazhafiz b824302ab3 Name resolved type variables during Expr2 constrain testing ... Prior to this patch we would not explicitly name solved type variables, causing the elaborated type to appear unconstrained even when the internal representation was constrained. For example, given a definition like ``` \a, b -> Pair a b ``` we would generate distinct, fresh type variables for `a` and `b` but not name them after solution. So even though the compiler knows they are distinct, printing to the surface syntax would emit ``` *, * -> [ Pair * * ]* ``` which is incorrect, as the result type is constrained on the input type. Instead, we now properly emit ``` a, b -> [ Pair a b ]* ``` naming variables where dependencies do exist. Where type variables are don't constrain anything else, we can and do continue to emit the wildcard type.		2021-11-16 11:56:39 -05:00
..
src	Name resolved type variables during Expr2 constrain testing	2021-11-16 11:56:39 -05:00
Cargo.toml	Make versions numbers consistent and matching the lock files	2021-11-06 13:24:45 -07:00