Tip: unittest-only artifacts should not be version(unittest) if used across modules

[Jeremy Powers via Digitalmars-d]

On Thu, Jun 11, 2015 at 11:09 PM, Andrei Alexandrescu via Digitalmars-d <
digitalmars-d at puremagic.com> wrote:

> Just ran into this with Phobos:
> https://github.com/D-Programming-Language/phobos/pull/3403
>

If unittest-only artifacts are not constrained to just unittest builds,
does this not make them open to be not unittest-only?

That is to say, if there is a method or whatever that is just for tests,
without marking it 'version(unittest)' how do you ensure it is not actually
used in the regular, shipped code?

Not sure best way to solve the across-module problem and still keep test
code restricted to tests... maybe instead put the shared test code in its
own module, and import with version(unittest).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20150612/0af8d217/attachment.html>