[jira] [Comment Edited] (THRIFT-1909) Java: Add compiler flag to use the "option pattern" for optional fields

["Wouter Lammers (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/THRIFT-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365710#comment-14365710 ] 

Wouter Lammers edited comment on THRIFT-1909 at 3/17/15 6:20 PM:
-----------------------------------------------------------------

I've manually rebased the patch to what is current. It would be nice to use java 8 optional instead of the custom Option type.


was (Author: wouterlammers):
I've manually rebased the patch to what is current. It would be nice to use java 8 optional instead of the custom Option type instead.

> 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, thrift-0.9.3-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)