Course contentsShow
← Java
Lesson 1429 of 2,87032. Streams API: Intermediate OperationsFree lesson

map with Method References

Leveraging method references like String::toUpperCase and Integer::parseInt for cleaner map operations.

map with Method References

What you'll learn: How to write cleaner, more readable map operations by using method references instead of lambda expressions.


The Core Idea

You've already seen map transform stream elements using lambda expressions like s -> s.toUpperCase() or n -> Integer.parseInt(n). But when your lambda only calls a single method on its parameter (or passes it to a single method), you can use a method reference instead—a shorthand that makes your code more concise and expressive.

Think of it like giving directions: instead of saying "take the string and apply the toUpperCase method to it," you simply point and say "toUpperCase." Java understands what you mean.

Common Method Reference Patterns with map

Instance Methods on the Parameter

When transforming each element by calling one of its methods:

Stream<String> names = Stream.of("alice", "bob", "charlie");
names.map(String::toUpperCase)  // instead of s -> s.toUpperCase()
     .forEach(System.out::println);

Static Methods

When passing each element to a static method:

Stream<String> numbers = Stream.of("10", "20", "30");
numbers.map(Integer::parseInt)  // instead of s -> Integer.parseInt(s)
       .forEach(System.out::println);

Why Use Method References?

  • Readability: String::toUpperCase is shorter and clearer than s -> s.toUpperCase()
  • Less noise: No need to declare parameter names
  • Intent over implementation: Focus on what you're doing, not how

Both approaches compile to the same bytecode—method references are purely syntactic sugar for single-method lambdas.

Key Takeaway: When your map operation calls a single method, use method references like String::toUpperCase or Integer::parseInt for cleaner, more readable stream pipelines.