On Fri, Feb 20, 2015 at 2:59 AM, Keean Schupke <[email protected]> wrote:
>
>
>> But arities inferred from definitions should be exported. Anyway we
>> shouldn't get into too much detail about linking in BitC. I don't
>> _know_ the details, and anyway it seems like another topic.
>
>
> The way I see it, the arities need to be explicit in the module interface
> definition. Hence requiring the concrete expression of arity in the type
> signature like:
>
> data module A = {
> f :: fn 'a 'a -> 'a -- arity is explicit in export
> }
>
More specifically: the arity of the function being exported must be part of
the exported signature. The arities of parameters and return values may or
can be abstract. This is fine, because an exported abstract function must
be specialized to a concrete form before it is used, and a concrete arity
will be determined as a result.
shap
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev
