implicit conversion of FunctionN to tupled Function1. now you can write ...

...the clearer syntax pipe.map{ ('x: String, 'y: String) => x + y } instead of pipe.map{ x: (String, String) => x._1 + x._2 }

not sure why this wasn't done before. perhaps there is a good reason for avoiding these implicits?
my observation is that this makes scalding a lot easier to write for the novice. as much as i prefer to use Function1 everywhere (support for andThen and such) the tupled Function1 syntax isn't always the most intuitive or the most concise.