On Sunday, 25 June 2017 at 10:53:35 UTC, Mike wrote:

I'm not really interested in that because its too blunt of an instrument. I'd like to use TypeInfo, but only if I'm doing dynamic casts or other things that require such runtime information. Also, I'd only want the TypeInfo for the types that need it in my binary. I've said this before but I'll repeat: I like TypeInfo; I just don't like dead code.

Just a little more information about this. It doesn't appear that the entire TypeInfo object is remaining in the binary. It appears to only be the `name` of the type that the linker just can't seem to "garbage collection" from the .rodata section.

Mike


Reply via email to