Java: TwitterTextParser creates unnecessary objects

[denisk20]

Every call to TwitterTextParser.parseTweet now creates a new TwitterTextParseResults object, which in turn has 2 nested Range objects. While this makes sense for server development it is a terrible pattern for mobile since garbage collection is much more expensive there. Please consider providing us with an overloaded parseTweet which will accept an outTwitterTextParseResult as a parameter.

[leeaustinadams]

Hoping to circle back to twitter-text issues next week (Feb 25th)

[leeaustinadams]

The problem with a mutable TwitterTextParseResults is that.. it's mutable. I haven't addressed this yet, not sure if it's still a concern.