Ayaz Hafiz 163c6b39d6 Unify type alias "real variables" ... Turns out that we can't always assume that a successful unification of type alias type variables means that those aliases had the same real type from the start. Because type variables may contain unbound type variables and grow during their unification (for example, `[InvalidNumStr]a ~ [ListWasEmpty]b` unify to give `[InvalidNumStr, ListWasEmpty]`), the real type may grow as well. For this reason, continue to explicitly unify alias real types for now. We can get away with not having to do so when the type variable unification causes no changes to the unification tree at all, but we don't have a great way to detect that right now (maybe snapshots?) Closes #2583		2022-04-05 11:21:52 -04:00
..
src	Unify type alias "real variables"	2022-04-05 11:21:52 -04:00
Cargo.toml	Treat rigids as flex vars when checking number range types	2022-02-06 15:04:12 -05:00