"Mistakes will be made, but that's good because it means decisions are being made." -- Steve Jobs
Now they will just need to grapple over with what kind of scoping that Java's lambdas will have.
Do you mean about how lambdas are implemented from a bytecode standpoint, or other types of issues?
For instance, there was a long battle over whether () would be enough to invoke a lambda, or whether some sort of apply() or invoke() or .() method would be required, and a lot of the problems with () come down to differences between the way fields and methods are inherited in Java, esp. w.r.t. shadowing. I don't even know how it all came down, but it gets nasty, a lot of this stuff just wasn't designed with lambdas in mind.