Workaround for typeid access violation

[Etienne Cimon via Digitalmars-d]

On Tuesday, 16 June 2015 at 22:21:28 UTC, Steven Schveighoffer 
wrote:
> If you want to manage memory from a GC'd object, you can use C 
> malloc and C free.
>
> Or, you can write your own GC that solves this problem that 
> Sun/Oracle couldn't :)
>
> In all seriousness, you could potentially have exceptions to 
> this rule, but it would take a lot of cajoling of druntime and 
> some funky @UDA magic.
>
> -Steve

Yeah, I'm going to make a personal branch and develop a GC 
thread-local, and ensure memory/vtbl is left intact during 
collection/finalization, it's a good experiment and I believe it 
will be a way to solve the issue in the near future. Of course, 
no support for moving shared objects in a foreign thread 
anymore.. like that was any useful in the first place :P