Comparator.reversed() does not compile using lambda

by

This is a weakness in the compiler’s type inferencing mechanism. In order to infer the type of u in the lambda, the target type for the lambda needs to be established. This is accomplished as follows. userList.sort() is expecting an argument of type Comparator<User>. In the first line, Comparator.comparing() needs to return Comparator<User>. This implies that Comparator.comparing() needs a Function that takes a User argument. Thus in the lambda on the first line, u must be of type User and everything works.

In the second and third lines, the target typing is disrupted by the presence of the call to reversed(). I’m not entirely sure why; both the receiver and the return type of reversed() are Comparator<T> so it seems like the target type should be propagated back to the receiver, but it isn’t. (Like I said, it’s a weakness.)

In the second line, the method reference provides additional type information that fills this gap. This information is absent from the third line, so the compiler infers u to be Object (the inference fallback of last resort), which fails.

Obviously if you can use a method reference, do that and it’ll work. Sometimes you can’t use a method reference, e.g., if you want to pass an additional parameter, so you have to use a lambda expression. In that case you’d provide an explicit parameter type in the lambda:

userList.sort(Comparator.comparing((User u) -> u.getName()).reversed());

It might be possible for the compiler to be enhanced to cover this case in a future release.

More Related Contents:

  1. What is the equivalent lambda expression for System.out::println
  2. Very confused by Java 8 Comparator type inference
  3. Java 8: Difference between method reference Bound Receiver and UnBound Receiver
  4. java.lang.NullPointerException is thrown using a method-reference but not a lambda expression
  5. Instance Method Reference and Lambda Parameters
  6. Java 8 chained method reference?
  7. Why can method reference use non-final variables?
  8. Comparator.comparing(…) of a nested field
  9. Difference between method reference Bound Receiver and Unbound Receiver
  10. Java8 Lambdas vs Anonymous classes
  11. What is a ‘SAM type’ in Java?
  12. What is the breakdown for Java’s lambda syntax?
  13. Java 8 method reference unhandled exception
  14. Lambda expression and method overloading doubts
  15. Java 8 lambda expression and first-class values
  16. How to dynamically do filtering in Java 8?
  17. Why can’t I throw an exception in a Java 8 lambda expression? [duplicate]
  18. Do lambda expressions have any use other than saving lines of code?
  19. What is a Java 8 Lambda Expression Compiled to? [duplicate]
  20. Why does Stream.allMatch() return true for an empty stream?
  21. Java idiom for lambdas with non-SAM interfaces
  22. Static context cannot access non-static in Collectors
  23. Implement recursive lambda function using Java 8
  24. Proper usage of Optional.ifPresent()
  25. java: Arrays.sort() with lambda expression
  26. Picking elements of a list until condition is met with Java 8 Lambdas
  27. Please Explain Java 8 Method Reference to instance Method using class name
  28. Why does this Java 8 lambda fail to compile?
  29. FunctionalInterface Comparator has 2 abstract methods
  30. Stream.peek() method in Java 8 vs Java 9

Leave a Comment