lint for D

[bearophile]

I think that having a separate lint, a separate code commenting tool, and a separate unittest controller, may be better, because putting such things into the compiler makes the development of the compiler slower (because I think it's better for Walter to focus on just the compiler, reducing and focusing his work), and such tools become slower.
On the other hand standard tools may be unfit for D or they be difficult to use (so they may not scale *down*. ddoc and D unittests scale down very well, I mean you can use them even if you write a 15-lines program and you have read nearly nothing about how to use them).
So I suggest to develop standard tools present in all D distributions, really easy and fast to use, with hooks from the compiler (so their syntax is good!) able to scale down, and developed/debugged by the community too. The purpose of such tools is to have something that can be used almost with no manual, fast, and reliable, and needing nearly nothing else.
For people that have to document a 10000+ lines program then they can use doxigen or one very powerful lint tool, developed by other people.
This is how Python works: built-in the std lib you find very easy to use tools for most purposes. But you often use external more powerful and less easy to use tools when you need something more refined.

Bye,
bearophile