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.
Jonathan
On Tuesday, March 31, 2015, Keean Schupke <[email protected]> wrote:
>
>
> On 31 March 2015 at 22:00, Jonathan S. Shapiro <[email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
>>
>> The definition of f is not in scope. The only thing we know about f is
>> inferred from the application. It's a parameter, initially typed with a
>> fresh type variable and then refined by inference from the two
>> applications I gave.
>>
>
> We either have the actual definition, or the imported type signature. What
> other option is there?
>
> K.
>
>
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev
