Generally, we've said that it could be possible, but we haven't made it so yet.
My personal preference would be not to support this. I understand the need for heterogeneous collections, but I think that "any" is a pretty broad category to allow in a collection and not have to compromise something. There is already a totally viable workaround, though - make a Union of the types you want in your collection, and then make the field list<YourUnion>. You get basically all the capabilities with very few drawbacks, plus the ability to include multiple logical "types" in the collection, not just physical types. Of course, if you literally need "any" possible object to go into the collection, then this won't do it for you. -Bryan On Sat, May 1, 2010 at 10:40 AM, Alex Boisvert <[email protected]> wrote: > Hi, > > I'd like to use an heterogeneous collection, e.g. list<any>, in a service. > > I see there's been some work/discussion on this earlier, > https://issues.apache.org/jira/browse/THRIFT-122 > https://issues.apache.org/jira/browse/THRIFT-110 > > Now THRIFT-110 is committed and claims to incorporate THRIFT-122. > > I've looked around but couldn't find the answer... how do I declare an > heterogeneous collection in a .thrift definition? > > alex >
