DUB 0.9.21 beta 1

[Kapps]

On Wednesday, 11 December 2013 at 22:13:59 UTC, Kapps wrote:
> I noticed that the main file generated seems to already support 
> tested integration automatically which I find quite nice. 
> Unfortunately it seems that tested is not actually following 
> imports so both the above sample and the auto-generated main 
> result in 0 tests being run as test_main does not directly 
> contain any tests. I've tried looking in to fixing this, but 
> it's proving a bit more tricky than expected and I won't have 
> much time for the next couple of days. Essentially, with 
> "static if (__traits(compiles, { auto tup = 
> TypeTuple!(__traits(getMember, composite, M)); }))" I don't 
> believe that that's ever true as assigning to tup like that is 
> an error. Changing that to check if the getMember succeeds will 
> then get past that, but now the recursive calls for 
> runUnitTestsImpl will operate on the return type of methods as 
> __traits(getMember, T, <somemethod>) returns the result of 
> invoking the method and not the method itself. I'm not sure how 
> to pass in an alias to the actual method rather than to the 
> return type.

Ah, I think I'm mistaken. What I assumed was that it was handling 
the return type of the function may have just been that it was 
going over aliases instead (which in this case would have been an 
alias to ulong and such, causing the above problems).