Context Navigation

Changes between Version 441 and Version 442 of TypeFunctionsStatus

v441	v442
11	11	* Issue a warning if there are two identical instances (as per Roman's suggestion).
12	12	* #2203 (TFs in class instance heads)
13		* #2435 (~~Bug with qualified names in~~ declarations)
	13	* #2435 (Inconsistency in handling qualification of names of class methods and associated types in instance declarations)
14	14	* Defaults for associated type synonyms. (Having both a kind signature and vanilla synonym is problematic as in `RnNames.getLocalDeclBinders` its hard to see that not both of them are defining declarations, which leads to a multiple declarations error. Defaults are quite different from vanilla synonyms anyway, as they usually have tyvars on their rhs that do not occur on the lhs.) If an associated synonym has a default definition, use that in the instances. In contrast to methods, this cannot be overridden by a specialised definition. (Confluence requires that any specialised version is extensionally the same as the default.)
15	15	* Can we add a warning in case of a signature that is ambiguous due to a type variable only been mentioned as an argument to a type synonym family?