Yes, I was thinking about that, and the Abstracttext implementation used to allow for implicit currying.
The advantage of *not* allowing implicit currying is that we have a stronger shape of the function call that we can test.
So, if implicit currying is forbidden, then any function call with fewer than the expected number of arguments becomes a validation error. We catch them early.
If implicit currying is allowed, all of these wouldn't be errors, but instead of an integer (or whatever), you suddenly get a function back.
I think the latter is potentially confusing and requires even beginners to be exposed to, well, curried functions and anonymous functions as return values.
If we require explicit currying, we don't lose any of the functionality - everything we could do before we still can do - but we lose some notational convenience for currying (which is kinda of a poweruser feature) but will probably catch much more errors than we would otherwise.
That would be my thoughts on implicit currying.
Denny