Policy for exposing range structs

[Steven Schveighoffer via Digitalmars-d]

On 3/31/16 10:30 AM, Adam D. Ruppe wrote:
> On Thursday, 31 March 2016 at 14:00:38 UTC, Steven Schveighoffer wrote:
>> Ugh, let's try the huffman coding thing first :)
>
> Do that after and along with!
>
>> Stack traces would be unusable.
>
> That's why I'd keep the function name outside the hash. The inner spam
> wouldn't be readable (not like a megabyte long name is readable
> anyway...), but the function name (which includes template arguments*)
> still is and that's probably the most useful part anyway.

Moving types outside the function actually results in a pretty readable 
stack trace.

I noticed the stack trace printer just gives up after so many characters 
anyway.

-Steve