On Sunday, 27 September 2015 at 05:01:48 UTC, Jonathan M Davis
wrote:
This DIP provides a way to handle unittest blocks inside of
templates which works with ddoc without compiling the unittest
blocks into each instantiation.
I understand that this DIP solves a genuine problem, so
understand that this bike-sheding comment is not a dismissal of
the idea.
I think it's a bad idea to further confuse what static means, as
it currently has no less than five different distinct uses.
* static ifs
* static array construction
* static assert
* static/shared static this
* static functions/data
Maybe a new keyword or some @attribute would make this clearer.
