LNK4255 warning when compiling examples under Windows 7 x86-64 about eventcore HOT 4 CLOSED

I've opened a workaround pull request, but it sounds like this should also be corrected in DMD itself. Since D has a module system, it would make sense to name object files according to their fully qualified name instead of just the module name itself.

from eventcore.

@s-ludwig hey, this issue is back unfortunately 😬

from eventcore.

Noticed that too, a few days ago. The good news is that it only influences debug data for the mentioned module. Everything else works as normal. So if stack traces do not show up, the cause is probably something else.

The right solution to me seems to be to let DMD name the modules according to their package hiearchy (e.g. "eventcore-driver.obj" instead of just "driver.obj"). That would also solve issues surrounding the "-op" switch, which is currently used by DUB to properly build projects that have this kind of name clash.

from eventcore.

The good news is that it only influences debug data for the mentioned module.

Ah, good to know! Stack traces do seem to be working fine, so it's mostly usable. Thanks for coming back to me!

from eventcore.