https://issues.dlang.org/show_bug.cgi?id=879
David Nadlinger <c...@klickverbot.at> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |c...@klickverbot.at
--- Comment #14 from David Nadlinger <c...@klickverbot.at> ---
I don't see how pinning the ModuleInfo reference from the ModuleInfo itself
would work, as there might not be any direct references to the ModuleInfo. In
fact, unless your module makes calls to _d_array_bounds or so, it's even rather
unlikely that such a reference that would keep the ModuleInfo alive exists.
Thus, the global ctor needs to keep the ModuleInfo alive (via the .minfo ref),
not the other way round.
--
