> You can put the module interface in a separate source file. You still
> want to compile it to metadata, unlike C/C++, so that you don't
> recompile it for each importing module. Also note that compiled code
> and metadata for a module don't need to be in the same file either.
>
I don't mind the compiler caching stuff, but its when you want to
distribute a binary library I would rather have a human readable header
file with the module interface and some comments, separate from the
implementation(s).
> 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
}
Keean.
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev
