Most issues will be tracked through Google Code's integrated issue tracker software, but I wanted to place a few items on their own wiki page so they would have more visibility. Here they are...

• There are a number of places in JSTraits where I need to represent sets (sets of exported methods, sets of required methods, etc.). For the most part I've implemented these using native JavaScript objects as hashes. This is certainly not the best data structure for the job because hashes do not usually lend themselves well to union, intersection, and enumeration operations. Ideally I would use some type of binary search tree or perhaps a skip list but . . . code size is an important factor (want to keep the size of a library to a minimum) and the current implementation seems to be zipping along. I'll need to create some good test cases and profile them before proceeding to determine if I need to optimize at all and what needs to be optimized.
• Need to further isolate the Class and Trait code so that the Trait code can be more easily incorporated in other Class implementations. There's no reason I shouldn't be able to reduce the interface to a method call or two in the class definition code.
• Need to bundle some standard traits with the code for use as an example and starting point for community trait libraries: TComparable, TEnumerable, TModal (for UI widgets), etc.).