[MLton] Few problems with porting...

[Matthew Fluet]

> We're there I'd say.  All of the front end is in place.  All that's
> left is bug reports at this point.  Which I eagerly await.

Not a bug report, per se, but some forward looking advice: I would suggest
pointing a prominent pointer in the changelog/release notes of the next
public release to the Deviations of SML/NJ from Standard ML section of the
user's guide.  In playing around with the new front-end on some old ML
code I had, I ran into a (documented) deviation in SML/NJ, which I at
first thought might be a MLton bug.