You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Mark Baker (JIRA)" <ji...@apache.org> on 2014/12/16 13:05:13 UTC
[jira] [Commented] (THRIFT-1909) Java: Add compiler flag to use the
"option pattern" for optional fields
[ https://issues.apache.org/jira/browse/THRIFT-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248185#comment-14248185 ]
Mark Baker commented on THRIFT-1909:
------------------------------------
+1 for this - we want to remove nulls from our Java code as in our Scala/Scrooge-generate code we prefer to use Option[T]
> Java: Add compiler flag to use the "option pattern" for optional fields
> -----------------------------------------------------------------------
>
> Key: THRIFT-1909
> URL: https://issues.apache.org/jira/browse/THRIFT-1909
> Project: Thrift
> Issue Type: New Feature
> Components: Java - Compiler, Java - Library
> Reporter: Eirik Sletteberg
> Attachments: add-option-type.patch
>
>
> This is a follow-up of the brainstorming issue about better null safety in Java.
> The patch adds:
> 1) A new abstract Option<T> class, with two subclasses: Some<T> and None<T>.
> 2) An optional compiler flag for the java compiler. When set, it wraps methods for optional fields in Option types.
> An example of usage is found here: https://github.com/eirslett/thrift-optional-example
> - No java dependencies are introduced.
> - The patch is entirely backwards-compatible; if the compiler flag is not present, it will generate the same code as thrift usually does.
> - The implementation is compatible with thrift servers/clients where the compiler flag is not used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)