Right now the uncurrying mechanism only takes one-arity into account. However, we usually remove the argument when this is of type unit, so we need to also consider zero-arity.
In JS this hasn't been a problem so far because if we pass an argument to a function without it will simply be ignored. However in Dart, and I assume in other typed languages too, if you try to pass a function like int Function() to an argument expecting int Function(Arg) (where Arg is a generic of the enclosing method), the compiler will complain.
Right now the uncurrying mechanism only takes one-arity into account. However, we usually remove the argument when this is of type
unit, so we need to also consider zero-arity.In JS this hasn't been a problem so far because if we pass an argument to a function without it will simply be ignored. However in Dart, and I assume in other typed languages too, if you try to pass a function like
int Function()to an argument expectingint Function(Arg)(whereArgis a generic of the enclosing method), the compiler will complain.