https://d.puremagic.com/issues/show_bug.cgi?id=12245
--- Comment #2 from Ivan Kazmenko <[email protected]> 2014-02-25 01:11:33 PST --- I think implying "unittest => slow but checked containers" is not the way to go, either. Imagine a module making heavy use of containers and just wishing to run the module's own unittests. With such implication, there would be no fast way to do that. Or is there a way to import the generic container from std.container without propagating the "-unittest" flag? It's a generic after all, so it can't be compiled separately, right? A better way would be to (create and) mention a version flag needed for container debugging in the documentation for the respective container. -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
