Currying in Perl 6 is not about saving keystrokes. It's about preserving abstraction, in the sense of letting you
factor out those parts of an interface you're not interested in. For that reason, I expect curried modules and classes to be more heavily used than curried functions.
It's also a bit of future proofing. I can pull in a module
or function and use it all over the place in my program. Then suppose the author of that module or function decides to add an additional optional parameter that happens to default the "wrong" way. I can override that bad default with a single curry, even if they added that bad parameter to every function in the module.
But we're not going to do implicit currying because we don't want the return type of a function to magically change just because someone tweaked the interface with an optional parameter or generalized one of the parameter types.
Doubtless there will be a way to implement implicit currying if you really want it, but it won't be the default.