[MLton] HOL's Moscow ML implementation, and pushing MLton to emulate it

Stephen Weeks MLton@mlton.org
Fri, 8 Apr 2005 15:39:06 -0700

> > Sure.  MLton represents a Real64.real list using 12 bytes per list
> > element, while it represents an Int32.int list using 8 bytes per list
> > element.
> In this case the universal rep is just a pair of pointers one to the head 
> and one to the tail... i.e. you can build that in constant time!

That is the universal representation of "real * real list", not "real
list".  It's the recursive type that causes problems.