On 1 April 2015 at 09:59, Jonathan S. Shapiro <[email protected]> wrote:
> I have answered this several times.
>
> f is a *parameter* whose only type information is a fresh type variable.
> For example:
>
> def keean f a b c d tst {
> if tst
> f a b
> else
> f a b c d
> }
>
> So no type signature of any kind for f, as I've said several times now.
> The procedure definition above is all you have to work with.
>
>
I thought that neither the Shapiro nor the Schupke scheme allowed
underapplied functions? Ie, disagreement on the native arity of `f` is a
type error.
--
William Leslie
Notice:
Likely much of this email is, by the nature of copyright, covered under
copyright law. You absolutely MAY reproduce any part of it in accordance
with the copyright law of the nation you are reading this in. Any attempt
to DENY YOU THOSE RIGHTS would be illegal without prior contractual
agreement.
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev
