Named unittests

[Andrei Alexandrescu]

On 5/18/19 4:32 PM, H. S. Teoh wrote:
> This is actually one of the big warts in D's otherwise very nice
> built-in unittests: when you compile with -unittest, it compiles ALL
> unittests, including those of 3rd party libraries that you really don't
> care about.  You*really*  want to be able to say "hey, compile*my*
> unittests, which are in modules X, Y, Z, and don't bother with
> everything else, 'cos they are external code that have already been
> unittested to death".  I'm really*not*  interested in running Phobos
> unittests for the 100th time which the CI's have already run 1000 times
> over, every single darned time I compile my own code!

Wait, if you build a program with -unittest will it run some/all of 
phobos' unittests? That would be indeed undesirable!

I wonder how often people compile external libraries together with the 
application within the same command line.