ModuleInfo, factories, and unittesting

[Atila Neves via Digitalmars-d]

On Thursday, 22 December 2016 at 17:46:06 UTC, Piotrek wrote:
> On Thursday, 22 December 2016 at 09:10:53 UTC, Walter Bright 
> wrote:
>> On 12/21/2016 11:24 PM, Walter Bright wrote:
>>>[...]
>>
>> Or have the compiler call a "registerUnittest()" function with 
>> a parameter that's the pointer to the unittest info. Of 
>> course, that would require that a registerUnittest function 
>> exists somewhere.
>
> I don't know what other people think but the current status of 
> build-in unittests are #1 issue for a quick development. The 
> inability to give test a name (plus selective unittesting) and  
> continue on failure is puzzling to me.
>
> Cheers,
> Piotrek

The worst is how useless plain `assert` is. But, all of these 
issues can (and have) be solved by libraries.

Atila