[MLton] Non-exhaustive exn fn match

Stephen Weeks MLton@mlton.org
Mon, 18 Jul 2005 17:35:48 -0700

> It was disabled because it made asserting whether or not execution was 
> currently in a critical section fail when the program failed to use 
> threads.

Yeah, I don't object to that at all.  It seemed like a fine tradeoff
in favor of maintenance sanity over performance.