News for hackers. Stuff that matters.
Re:The Current State of Java Value Types by bluejekyll on Thursday June 21, 2018 @12:01PM (#17366336)
The thing I realized, that may not be obvious, is that this allows for a “real” Optional type in Java, where the Option itself can not be null. This will allow us to remove bare null usage from existing and future Java codebases, without the annoyance of checking if the Option itself is null.

I hope that there will be a compiler flag at some point to enable a warning or compiler failure on any bare null usage.

Re:The Current State of Java Value Types by pjmlp on Thursday June 21, 2018 @01:29PM (#17367306)
That is the plan.

In a few of Java Language Summit talks, they mention about such cases.

Re:The Current State of Java Value Types by he0001 on Friday June 22, 2018 @04:59AM (#17372534)
How does that work in the case of fex Map<String,Optional<String>>?
Re:The Current State of Java Value Types by pjmlp on Friday June 22, 2018 @07:23AM (#17373103)
In the new world of Java value types, generics will support specialization for them.

"Adventures in Parametric Polymorphism" from Brian Goetz at JVM Language Summit 2016.

http://www.oracle.com/technetwork/java/javase/community/jlss...