I was more concerned about domain objects that might contain large numbers of optional elements. It seems such cases would need either Optional or @Nullable? ________________________________________ From: Andrew Phillips [aphill...@qrmedia.com] Sent: Wednesday, July 09, 2014 3:39 PM To: dev@jclouds.apache.org Subject: RE: Primitive types in APIs?
> Also, while 3 valued logic is great, it isn't supported that well in > Java (until Some/None/Option in Java 8, which helps some). jclouds is quite fond of Guava's Optional, but at the API level we mainly use it to allow access to extension APIs that are, well, optional. I'd agree that we don't really want Optional<...> as a return type for API calls that return a primitive value. Thanks for the input, Martin! ap
