> 
> This the use of "and". In mutually recursive type definitions, other
> types are not "known" during the definition, and as a result their
> representation cannot be used for optimization. I think this is true
> for all ocaml releases, but it is specified nowhere, and could be
> wrong.
> Since you're not going to write the first defintion anyway, this
> shouldn't be a real problem.
> The real problem is that when you use a signature like
>   sig type t type r = {f:t} end
> in a functor, then this signature cannot be instanciated by the
> unboxed version of r when t = float. And there is no way to solve it
> short of inlining functors.

And when will their be inlining of functors !!!

This is really needed to benefit both from
- High level programming using modules and functors
- the necessary (I really mean necesasry) optimization for float

> Cheers,
> 
> Jacques Garrigue
> -------------------
> To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
> Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


-- 
Christophe Raffalli
Université de Savoie
Batiment Le Chablais, bureau 21
73376 Le Bourget-du-Lac Cedex

tél: (33) 4 79 75 81 03
fax: (33) 4 79 75 87 42
mail: Christophe.Raffalli@univ-savoie.fr
www: http://www.lama.univ-savoie.fr/~RAFFALLI
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners