Utah Valley University teaches D (using TDPL)

[Sean Kelly]

bearophile Wrote:
> 
> He also gives a quite useful unittest that the student implementation must pass, this is a good usage of unittests. The unit test ends like this:
> 
> ...
>     writeln("unit test passed");
> }
> 
> Indeed, a person needs feedback that the unittests have run (and have succeed), I have used similar things in my dlbs1 (but more refined). This kind of need for feedback is so natural that something like that will be better somehow done on default by D.

I'd like unit tests to be optionally named: unittest("name").  The rest could then be done in library code.