Easy question :)

[Stephen Weeks]

> Nope.. I need to run a few  larger benchmarks to graduate. I avoided them in
> the past  because the larger benchmakrs  caused an older version of MLTon's
> optimizer to break. I'm hoping the newer version won't break. :)

Me too.  I'd hate to be responsible for stopping someone's (other than mine :-)
thesis.

> I don't mind if function arguments get reversed. It's the tuple layouts that
> need to stay in the "obvious" order. 

The same comment I made about function arguments applies to tuples.

> I hacked the  flattening code and changed a few List.fold's to List.foldr's
> and things seem to be working for me again... 

Good enough, but no guarantees you won't encounter more of the same problem in
the newer versions.  It seems more robust to me to look at all the tuple
components than to change the optimizer.