Re: [Caml-list] Why should I use .mli files?

[Edgar Friendly <thelema314@gmail.com>]

On 10/31/2012 9:38 AM, Daniel Bünzli wrote:
> The problem is not for a single value. The problem is understanding 
> what this modules actually exports and hence the information flow 
> between the larger program and that module. With this proposal that 
> information is scattered across the whole module among intermediary, 
> hidden, definitions.
>
> An mli summarizes very well the actual interface of the module without 
> being distracted by the way the code is actually organized in the 
> module. It's a huge tool for understanding programs.
> Best,
>
> Daniel
Ah, I misunderstood your criticism.  You're right, we should keep .mli 
files as the great summary of the interface of .ml files.  I'm pretty 
neutral about having type declarations (val foo : <type of foo>) in the 
.ml file, as this is just another duplication of what needs to be in the 
.mli file.  I think that the information in the .mli file should 
directly impact the compilation of the .ml file, in that types declared 
there should be available in the .ml file, and the types given to 
identifiers should be applied to bindings for those identifiers as 
they're being compiled (so that int specialization can produce better 
compiled code, for one example).

E.