Annoying deprecation messages when using EnumMembers with enum that has deprecated members

[Jonathan M Davis]

On Wednesday, October 9, 2019 1:58:56 AM MDT Seb via Digitalmars-d wrote:
> On Wednesday, 9 October 2019 at 07:24:04 UTC, FeepingCreature
>
> wrote:
> > On Tuesday, 8 October 2019 at 16:03:20 UTC, Jonathan M Davis
> >
> > wrote:
> >> I don't know enough of the details about how the unit test
> >> stuff works to say how it should be fixed, but I agree that
> >> the current behavior isn't great for alternate test runners.
> >>
> >> - Jonathan M Davis
> >
> > Maybe just ignore the deprecation if we're calling a function
> > that's a unittest?
>
> If you want to test deprecated features, you can mark the
> unittest as deprecated too.
>
>
> deprecated unittest { ... }
>
> This won't result in deprecations of the unittest's code block
> triggered.
> Example: https://run.dlang.io/is/eRxCtd

If I understand his complaint correctly, deprecated unittest blocks result
in deprecation messages when you use third party test runners instead of the
default one, and if that's what's happening, that should probably be fixed.

- Jonathan M Davis