Policy for exposing range structs

Steven Schveighoffer via Digitalmars-d digitalmars-d at puremagic.com
Thu Mar 31 07:00:38 PDT 2016


On 3/31/16 9:38 AM, Adam D. Ruppe wrote:
> On Thursday, 31 March 2016 at 13:10:49 UTC, Steven Schveighoffer wrote:
>> Voldemort types are what cause the bloat, templates inside templates
>> aren't as much of a problem.
>
>
> So here's an idea of other things don't work out: voldemort types don't
> have a name that can be said... that could be true in the mangle too.
>
> We could potentially just hash it to some fixed length. Take the
> existing name, SHA1 it, and call the mangle
> function_containing_type$that_hash. Demangling the inside is useless
> anyway, so we lose nothing from that.

Ugh, let's try the huffman coding thing first :) Stack traces would be 
unusable.

However, this does seem promising if that doesn't work out. The hash 
would definitely solve the linking and binary size issue.

A possible thing the compiler *could* do is place inside the binary a 
hash-to-actual-symbol table that the exception printer can utilize to 
print a nicer stack trace...

-Steve


More information about the Digitalmars-d mailing list