🚀 go-pugleaf

      datatype foo = FOO of x
      fun bar FOO x = x

	     (     )
   Missing parens, of course; you didn't really want a curried function
   of type (x -> foo) -> 'a -> 'a, did you? What's the problem? Anyone
   who's done much work in SML should recognise immediately that

	   fun bar x y = 

   defines a curried function.

Why _do_ people continue to use curried syntax when they just want a
function with several arguments? It's difficult to optimize for the
compiler, it gives uninformative type signatures (is "'a -> 'a -> 'a"
intended to be a function of one argument returning a function, or is
it intended to be a function of two arguments returning a "'a"?), it's
not what most programmers are used to, and it seems to be difficult to
indent automatically as well.

When I started using SML, I found curried syntax "cute" for, but after
a few months, I began to find it rather bothersome, and now, I have
completely switched over to tupled syntax (including my own "standard"
library).

					Thomas.