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

[FeepingCreature]

On Wednesday, 9 October 2019 at 08:28:00 UTC, Jonathan M Davis 
wrote:
> 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:
>> > 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

That's correct. It's not been a problem in the past since 
deprecations were ignored in mixins, so unit-threaded worked "by 
coincidence."