[
https://issues.apache.org/jira/browse/THRIFT-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268270#comment-14268270
]
Jens Geyer commented on THRIFT-1854:
------------------------------------
How can this made available in a language-agnostic way? I mean, we support
something around 20 languages now and striving for a consistent way throughout
all of them seems important to me. Otherwise, soner or later will will end up
with lots of different implementations.
Without a doubt having a handy, flexible tool is very valuable. On the other
hand, [Simplicity, Transparency, Consistency and
Performance|https://thrift.apache.org/about] are valuable goods too. We should
keep that in mind, IMHO.
> trove support for lists of primitives
> -------------------------------------
>
> Key: THRIFT-1854
> URL: https://issues.apache.org/jira/browse/THRIFT-1854
> Project: Thrift
> Issue Type: New Feature
> Components: Java - Compiler
> Reporter: Vitali Lovich
> Attachments:
> 0001-Add-support-for-trove-option-to-Java-generator.patch,
> 0002-adding-support-to-use-Trove-lists-instead-of-native-.patch,
> 0003-Implement-trove-support-for-sets.patch,
> 0004-Implement-trove-support-for-maps.patch
>
>
> When dealing with large collections of primitive types, there can be
> significant memory (i.e. using arrays of objects instead of arrays of
> primitives) & runtime overhead (autoboxing/unboxing) using the default
> collections. Utilizing trove can significantly improve things. ideally
> support would be added for sets & maps, but as a first pass lists would be
> great.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
