[ https://issues.apache.org/jira/browse/THRIFT-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268624#comment-14268624 ]
Vitali Lovich commented on THRIFT-1854: --------------------------------------- It wouldn't make sense to bundle trove into a release. Let the end-user make that decision. What would a generic implementation look like? I've heard this multiple times in this thread but there hasn't been any kind of proposal put forward on what such a workable solution would look like. I'm not a full-time thrift developer so I'm not going to have the best set of information to inform any kind of design. > 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)