Java Streams Interview Trap: map() vs mapToInt() vs mapToDouble() Explained

If you’re working with a Stream<T> (objects), you must convert it to a primitive stream (IntStream, DoubleStream, etc.) before calling average().

🧠 Interview-Level Understanding

✔ Rule of Thumb

• Object Stream (Stream<Employee>) → ❌ no average()
• Primitive Stream (IntStream, DoubleStream) → ✅ has average()

👉 So conversion is required when your stream contains objects

🔍 Case-Based Explanation

✅ Case 1: Object Stream (Your Example)

employees.stream()              // Stream<Employee>
    .mapToDouble(e -> e.getSalary())   // DoubleStream ✅
    .average();

✔ Required → because Employee is an object

✅ Case 2: Already a Primitive Stream

IntStream.of(10, 20, 30)
    .average();   // ✅ No conversion needed

✔ Not required → already IntStream

❌ Case 3: Using map() instead of mapToX()

employees.stream()
    .map(e -> e.getSalary())   // Stream<Double> ❌
    .average();                // ❌ Compile error

👉 map() keeps it as object stream, not primitive

🔥 Important Interview Insight

Why Java Forces This?

1. Performance Optimization
   • Primitive streams avoid boxing/unboxing
   • Faster operations
2. Specialized Methods
   • average(), sum(), min(), max() exist only in:
     • IntStream
     • LongStream
     • DoubleStream

⚡ Quick Cheat Sheet

Situation	Need mapToX()?
Stream<Employee>	✅ Yes
Stream<Integer>	✅ Yes
IntStream	❌ No
DoubleStream	❌ No

🚀 Final Takeaway (Interview Ready)

“Whenever I’m working with a Stream of objects and need numeric aggregation like average, I must convert it into a primitive stream using mapToInt, mapToDouble, or mapToLong. Otherwise, average() won’t be available.”