[ https://issues.apache.org/jira/browse/THRIFT-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268335#comment-14268335 ]
Jake Farrell commented on THRIFT-1854: -------------------------------------- I'm still not in favor of committing this as it stands and would like to see a more generic implementation that did not pin it to just trove support. Also trove is LGPL which we would not be able to include [1] in any releases [1]: http://www.apache.org/legal/resolved.html#category-x > 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)