Reconsider the usage of `Optional<T>` in our API

The early API such as Scheme.tryParse() and Server.activePort() returns an Optional while more recent APIs just return null.

Given that Optional tends to make user code verbose and JDK will nor make Optional a value type due to backward compatibility (which is a shame…), I think it’s better just returning a nullable value.

This guarantees breaking changes, but migration should be as simple as wrapping with Optional.ofNullable(), so … 😅

[minwoox]

Let’s get rid of all of’em!

[trustin]

Hi @alex-lx! Value types are ‘inline classes’:

• https://www.infoq.com/articles/inline-classes-java/
• https://dzone.com/articles/project-valhalla-fast-and-furious-java

Optional is not an inline class and I guess it will never be so due to backward compatibility reasons.

A user who prefers method chaining with Optional could wrap the return value with Optional.ofNullable(...), although it’s verbose. I wish Java introduces operators like ?, ?. ?: once Project Valhalla is ready.