17

This is my code

    List<Integer> ints = Stream.of(1,2,4,3,5).collect(Collectors.toList());
    Integer maxInt = ints.stream()
                              .max(Comparator.comparing(i -> i))
                              .get();

    System.out.println("Maximum number in the set is " + maxInt);

output:

Maximum number in the set is 5

I cannot make distingues between two i in below section of my code

Comparator.comparing(i -> i)

can anyone be kind and explain the difference between two i?

Improve this question

3 Answers 3

Reset to default
25

The method Comparator.comparing(…) is intended to create a Comparator which uses an order based on a property of the objects to compare. When using the lambda expression i -> i, which is a short writing for (int i) -> { return i; } here, as a property provider function, the resulting Comparator will compare the values itself. This works when the objects to compare have a natural order as Integer has.

So

Stream.of(1,2,4,3,5).max(Comparator.comparing(i -> i))
.ifPresent(maxInt->System.out.println("Maximum number in the set is " + maxInt));

does the same as

Stream.of(1,2,4,3,5).max(Comparator.naturalOrder())
.ifPresent(maxInt->System.out.println("Maximum number in the set is " + maxInt));

though the latter is more efficient as it is implemented as singleton for all types which have a natural order (and implement Comparable).

The reason why max requires a Comparator at all, is because you are using the generic class Stream which might contain arbitrary objects.

This allows, e.g. to use it like streamOfPoints.max(Comparator.comparing(p->p.x)) to find the point with the largest x value while Point itself does not have a natural order. Or do something like streamOfPersons.sorted(Comparator.comparing(Person::getAge)).

When using the specialized IntStream you can use the natural order directly which is likely to be more efficient:

IntStream.of(1,2,4,3,5).max()
.ifPresent(maxInt->System.out.println("Maximum number in the set is " + maxInt));

To illustrate the difference between “natural order” and a property based order:

Stream.of("a","bb","aaa","z","b").max(Comparator.naturalOrder())
.ifPresent(max->System.out.println("Maximum string in the set is " + max));

this will print

Maximum string in the set is z

as the natural order of Strings is the lexicographical order where z is greater than b which is greater than a

On the other hand

Stream.of("a","bb","aaa","z","b").max(Comparator.comparing(s->s.length()))
.ifPresent(max->System.out.println("Maximum string in the set is " + max));

will print

Maximum string in the set is aaa

as aaa has the maximum length of all Strings in the stream. This is the intended use case for Comparator.comparing which can be made even more readable when using method references, i.e. Comparator.comparing(String::length) which almost speaks for itself…

Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

what do you mean natural order? can you break it down with a sample?what do you mean it compares value to itself? can u break it down with a sample?
so in this case i -> i is kind of redundant ?
Yes, as said, it does the same as Comparator.naturalOrder(). So for IntStream you can even omit the Comparator and achieve the same.
i posted my answer as a question, so could you take a look at it and share your thought with me? stackoverflow.com/questions/24399181/…
5

This function (note -> is for closures and not to be confused with => which is for comparison)

i -> i

just means you need to compare the entire object as it is. i.e. if I have an i you need to compare i

A less trivial example might be

max(Comparator.comparing(i -> -i))

which will give you the minimum or

max(Comparator.comparing(i -> Math.abs(100-i))

gives you a value which is farthest from 100.

max(Comparator.comparing(i -> i.toString()))

which will give you the maximum comparing as a String i.e. "9" > "10" as a string.

Improve this answer

17 Comments

Let us continue this discussion in chat.
=> is comparison, -> is a closure.
@KickButtowski Do you mean the oracle tutorial on Lambdas I linked to a few comments back? ;) Say these words " -> is NOT a comparison ". I have said this twice now.
Just recall that i -> i is a short writing for (int i) -> { return i; }. By looking at the longer form it should become clear what happens…
@Kick Buttowski: nothing happens to i. The specified function is only used to determine the ordering property for the Comparator. If the specified function returns just the value itself it implies that the natural order of the values is used. This is obsolete as Comparator.naturalOrder() would do the same. But if you return -i instead it would reverse the order. And if you use i -> Integer.bitCount(i) it would sort int numbers by their bit count.
|
0

Comparator.comparing expects a function which maps the source object to the value which actually gets compared - in your case, as you don't want to pre-process the value to be compared, i is simply mapped to itself.

Improve this answer

10 Comments

can you either explain more or provide me a source so I can read about it?
Which part of my answer didn't you understand?
Comparator.comparing expects a function which maps the source object to the value which actually gets compared -
can you add a diagram to show the relationship of two I i->i
the two i are identical - Comparator.comparing expects a function to be applied on every input element and as the function i -> i describes that you take every input and return itself as an output, the values to compare are not transformed.
|

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.