fix type checking of existential type variables that are used by a dynamic expression,
but do not occur in the type of a dynamic pattern.
TempQDV is used for existential type variables in a dynamic pattern.

use a separate list of function and macro declarations (to have fewer differences with the branches)

but do not occur in the type of a dynamic pattern.
TempQDV is used for existential type variables in a dynamic pattern.

but do not occur in the type of a dynamic pattern.
TempQDV is used for existential type variables in a dynamic pattern.

because function pointers for generated functions are stored in the Component,
they can be found without searching the new functions list

get_linearity_info, get_linearity_info_of_pattern, get_var_index, set_linearity_info

constructors with only type variable arguments occurring at most once,
these types can be optimized if they occur as an argument or result,
or as an argument of such a type, of a generic function (and a generic
variable is used by the type)

call instance functions for OBJECT, CONS and FIELD directly, with generic info

first all main instances are build, then all shorthand instances,
shorthand instances directly call the main instance (SK_Function instead of SK_Generic),
call toGeneric.. and fromGeneric.. functions directly if possible, instead of iso..

add BETypeSymbolNoMark

No commit message

instead of scanning all constructors to find it in BERecordType,
(should be passed directly to BERecordType)

No commit message

don;t write generic dictionaries to these files

No commit message

because OBJECT, CONS and FIELD have this kind and are the only types using generic info

fix error message for failed qualified import

because it is always []