unittests are really part of the build, not a special run

[ketmar via Digitalmars-d]

On Wed, 01 Apr 2015 19:18:52 +0000, Kapps wrote:

> Everything you propose can be done with a custom unittest runner, using
> the builtin unittest blocks. Compile-time reflection + UDAs + unittests
> is a surprisingly powerful combination, and I don't understand the
> proposals to make unittest name and such part of the ModuleInfo or
> provide special compiler support for them. Such an approach is not as
> scalable, and with compile-time reflection you can do anything you need
> with the current built-in unittest blocks.

only if reflection is fully working, which is not the case (see, for 
example, old bug with member enumeration for packages).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20150401/bcadf3d3/attachment.sig>