Mailing-List: contact thrift-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: thrift-dev@incubator.apache.org
Message-ID: <1448878380.1239174972989.JavaMail.jira@brutus>
Date: Wed, 8 Apr 2009 00:16:12 -0700 (PDT)
From: "Chad Walters (JIRA)" <jira@apache.org>
To: thrift-dev@incubator.apache.org
Subject: [jira] Commented: (THRIFT-413) Type annotations for base types
In-Reply-To: <1251953723.1238467670420.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chad Walters commented on THRIFT-413:
-------------------------------------

+1 lgtm

> Type annotations for base types
> -------------------------------
>
>                 Key: THRIFT-413
>                 URL: https://issues.apache.org/jira/browse/THRIFT-413
>             Project: Thrift
>          Issue Type: Improvement
>            Reporter: David Reiss
>            Priority: Minor
>         Attachments: 0001-THRIFT-413.-Suppport-for-annotations-on-base-types.patch
>
>
> This patch allows type annotations to be applied to base types.  The one thing about it that scared me a bit was that we were allocating a new type object for each base type with annotations, so checks like
> {code}
> if (get_true_type(ttype) == g_type_i32)
> {code}
> would fail if ttype had annotations.  But I grepped for all uses of the global type objects and didn't find anything like that.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.