When I need to use Optional.orElseGet() over Optional.orElse()

by

I think I am starting to understand your question. Execution order with Optional can be different from what we are used to in procedural programming (the same is true for Java streams and other code using lambdas).

I will use the two examples from Eugene’s answer:

    o1.orElse(new MyObject()); // 1055e4af

This is plain old Java: it’s a call to orElse() taking new MyObject() as argument. So the argument is evaluated first and a new MyObject created. This is then passed to orElse(). orElse() looks to see whether a value is present in the Optional; if so it returns that value (discarding the newly created object); if not, it returns the object given to it in the argument. This was the simpler example.

    o1.orElseGet(() -> {
        System.out.println("Should I see this");
        return new MyObject();
    });

Again we have a method call with one argument, and again the argument is evaluated first. The lambda is only created and passed as a supplier. The code inside { } is not executed yet (you also see no Should I see this in Eugene’s output). Again orElseGet looks to see if there is a value present in the Optional. If there is, the value is returned and the supplier we passed is ignored. If there isn’t, the supplier is invoked, the code inside { } is executed to get the value to be returned from orElseGet().

In the first case, one may say that a MyObject is created and wasted. In the second a Supplier is created and wasted. What you get in return is terse and null-pointer safe code in both cases. So very often it’s not important which one you pick. If creating the MyObject is costly or has unwanted side effects, you will of course want the second version where the object is only created when it is asked for, and is never wasted. Eugene in a comment mentions the case where the returned object comes from a database call. Database calls are usually time-consuming enough that you don’t want to make one for no purpose.

More Related Contents:

  1. Why use Optional.of over Optional.ofNullable?
  2. Why does findFirst() throw a NullPointerException if the first element it finds is null?
  3. Get value from one Optional or another
  4. Valid usage of Optional type in Java 8
  5. Should Optional.ofNullable() be used for null check?
  6. Proper usage of Optional.ifPresent()
  7. ‘Optional.get()’ without ‘isPresent()’ check
  8. How to execute logic on Optional if not present?
  9. Java 8’s orElse not working as expected
  10. Is it a good practice to use Optional as an attribute in a class? [duplicate]
  11. Get List<K> from HashMap<K, V> where V is instance of I [closed]
  12. Java 8 Distinct by property
  13. What are functional interfaces used for in Java 8?
  14. Why filter() after flatMap() is “not completely” lazy in Java streams?
  15. What is the equivalent lambda expression for System.out::println
  16. Difference between `Optional.orElse()` and `Optional.orElseGet()`
  17. Generic type inference not working with method chaining?
  18. Maven is not working in Java 8 when Javadoc tags are incomplete
  19. Removing Java 8 JDK from Mac
  20. Why is a combiner needed for reduce method that converts type in java 8
  21. Java 8: Where is TriFunction (and kin) in java.util.function? Or what is the alternative?
  22. Performance difference between Java 8 lambdas and anonymous inner classes
  23. Java 8 method references: provide a Supplier capable of supplying a parameterized result
  24. Mock Instant.now() without using Clock into Constructor or without Clock Object
  25. Adding a line in a JavaFX chart
  26. LocalDate to java.util.Date and vice versa simplest conversion? [duplicate]
  27. Is mapToDouble() really necessary for summing a List with Java 8 streams?
  28. Is it possible to cast a Stream in Java 8?
  29. Spring + AspectJ weaving for java 8 using aspectj-maven-plugin
  30. Visualization of Java Stream parallelization

Leave a Comment