| > The variables bound in a case alternative are the [b] in CoreSyn.Alt.
| > These binders include all the type variables, coercion variables, and
| > value variables bound in the alternative.
|
| Are there any rules about the order in which the different types of
| variables appear (e.g.,
Simon Peyton-Jones writes:
> | I assume this is only the
> | value variables, and that the type/coercion variables come from
> | DataCon.{dataConExTyVars,dcEqSpec}, right?
>
> Not so at all. Why did you assume that?
You're right, that was a silly assumption. However, without it, I
| CoreSyn.AltCon includes a list of Var's -- I assume this is only the
| value variables, and that the type/coercion variables come from
| DataCon.{dataConExTyVars,dcEqSpec}, right?
Not so at all. Why did you assume that? The variables bound in a case
alternative are the [b] in Core
1. In SystemFC a case branch binds three sorts of variables: type variables
(for the existential types of the relevant DataCon), coercion variables
(similar), and value variables (for the fields of the DataCon).
CoreSyn.AltCon includes a list of Var's -- I assume this is only the
valu
