Named unittests and __traits(getModules)

[Jacob Carlborg]

On 2019-05-23 22:42, Andre Pany wrote:

> One thing I do not understand. Once module A, which contains the new 
> traits, is compiled using separate compilation, the list of found 
> modules is fixed. If now new module B is added, nothing will cause a 
> rebuild of A and therefore the list of found modules is incomplete.
> 
> This can of course be solved by telling the user to not use separate 
> compilation, which might be a fair tradeoff, I am not sure.

It works with separate compilation if the unit tests are collected into 
a global variable. Here's an example using the existing 
__traits(allMembers):

$ cat main.d
module bar;

extern (C) __gshared string[] members;

void main()
{
     import foo;

     members ~= [__traits(allMembers, bar)];
     foobar();
     assert(members == ["object", "members", "main", "object", 
"members", "foobar"]);
}

$ cat foo.d
module foo;

extern (C) extern __gshared string[] members;

void foobar()
{
     members ~= [__traits(allMembers, foo)];
}

$ dmd -c foo.d && dmd foo.o -run main.d

The assertion passes as expected.

-- 
/Jacob Carlborg