Java中Optional类被声明为final的原因是什么？

Excellent observation! You’re totally correct that with all constructors of Optional<T> being private:

private Optional(T value) { this.value = Objects.requireNonNull(value); }
private Optional() { this.value = null; }

user code can’t subclass it at all—even without the final modifier. So why mark it as final?

Let’s break this down, especially comparing it to Scala’s Option (a sealed class implemented by Some and None):

First, it’s worth noting that when Optional was added in Java 8, sealed classes didn’t exist in Java (they arrived in Java 17). Back then, the most reliable way to guarantee a class couldn’t be subclassed—either by external code or even accidentally within the JDK itself—was to combine private constructors with the final modifier.

But even beyond historical context, there are practical reasons:

• Clear contract enforcement: Marking Optional as final leaves no room for ambiguity. Developers know that every Optional instance behaves exactly as defined by the JDK; there’s no chance of a subclass overriding methods and changing expected behavior. This aligns with Optional’s role as a utility class for safe null handling, where consistency is key.
• Immutability guarantee: Optional is designed to be immutable. Making it final reinforces this—you can’t create a mutable subclass that breaks this guarantee, even if someone tried to work around the private constructors (though that’s not possible here, it’s an extra layer of safety).
• Simplicity in implementation: The Java team might have chosen this approach to keep the Optional codebase straightforward. Instead of managing internal subclasses like Some and None, they opted for a single final class with static factory methods (of, empty, ofNullable) that handle the presence/absence of values internally.

That said, using private static subclasses (like Scala does) would have been a valid alternative. But the final approach fits well with Java’s design philosophy of explicit, robust guarantees for core library classes.

内容的提问来源于stack exchange，提问作者St.Antario