In perl, a thrift set<> type should use a more proper native implementation

Currently a set<> type in Thrift equates to a hash where the value of each type is set to 1. The keys are interpreted as strings and therefore lose their ordering. The TestClient for cpp sends:

The TestServer for perl (which I am writing to verify SSL server refactoring) receives:

$thing HASH(0x35da228)=

Note how -1 and -2 are transposed. Further, there are no set manipulations available.

Recommend the use of Set::Scalar as a required perl dependency for proper set operations.
The old behavior could be preserved through a compiler flag for perl ensuring that existing products that rely on the current implementation don't have to change.