GitLab

Fix == for TypeCons, fixing a bug where multiple alternatives of some generic...

Closes #55

See merge request clean-compiler-and-rts/compiler!12

Fix == for TypeCons, fixing a bug where multiple alternatives of some generic cases were not allowed

restrict default instances to instances with at least one type variable argument, only type constructors at the root, and all type variables are used once, fix instance lookup of other instances: search if no instance was found in the instance group

remove old overlapping instance test, change find instance algorithm, first determine if an instance exists that only has type constructors as root types (monomorphic root), if so try to find the instance in this group, otherwise try the other instances (polymorphic root)

fix type synonym expansion error in new code for: add new check for overlapping instances (commit 00e07f57)

Resolve crash on existentially qualified type variables that already appear in...

Closes #50

See merge request clean-compiler-and-rts/compiler!11

Resolve crash on existentially qualified type variables that already appear in the left-hand side of the type

generate bimap functions as a case with for each constructor as result the constructor with bimapped arguments, no generic representation of the algebraic, record or newtype is created, remove the bimap functions for the generic representation constructors, use a seperate type for the GenTypeStruct for bimap (BimapGenTypeStruct)

move types GenTypeStruct and GenericTypeRep from module syntax to module generics1, make type GenericTypeReps extensible and move constructors except NoGenericTypeReps

Add error location for patterns in list comprehensions

See merge request clean-compiler-and-rts/compiler!8

using bimap when deriving generic functions

A simple bimap function is generated for a type if each constructor argument or field
	- is the only occurrence of a type variable in this constructor or record or
	- consists only of basic types and type constructor names (does not contain type variables)

For example for tuple and Maybe types.

A more complicated bimap function is generated for a type if each constructor argument or field
	- is a type variable
	- consists only of basic types and type constructor names (no type variables)
	- a function type a->b where either a or b
	  is a type that satisfies these rules and the other type
	  consists only of basic types and type constructor names (no type variables)
	- a type constructor for which a simple bimap function can be generated
	  with one argument of which the type satisfied these rules, and the other arguments
	  consist only of basic types and type constructor names (no type variables)

For example for a record with function types with a single type variable.

fix commit f9eda3c5, add code to handle optimized derive of bimap for constructor arguments that do not contain a type variable

extend the number of cases in which a function is generated instead of using bimap when deriving generic functions, also permit some records

in module generics1, use bimap_from_simple_type and bimap_to_simple_type also for partial function calls

extend the number of cases in which a function is generated instead of using bimap when deriving generic functions, also permit constructor arguments that do not contain a type variable

removed optional type context in an import of an instance, it is not required and was ignored by the compiler

Add error and warning "unused existentially quantified type variable"

Closes #44

See merge request clean-compiler-and-rts/compiler!6

Prevent runtime error on illegal type arguments in generic function definitions

Closes #43

See merge request clean-compiler-and-rts/compiler!5

add optimizations that creates specialized zero arity functions for partial function applications with all arguments only zero arity functions or constructors or integer or string denotations, generic derive often generates these function applications