Policy for exposing range structs

[Adam D. Ruppe via Digitalmars-d]

On Thursday, 31 March 2016 at 17:30:44 UTC, Anon wrote:
> My encoding is shorter in the typical use case


Yeah, but my thought is the typical use case isn't actually the 
problem - it is OK as it is. Longer strings are where it gets 
concerning to me.

> Would a hybrid approach (my encoding, optionally using 
> compression when it would be advantageous) make sense?

Yeah, that might be cool too.

> Alternately, we could do the compression on whole mangled 
> names, not just the string values, but I don't know how 
> desirable that is.

There are often a lot of repeats in there... so maybe.