Enhancement: issue error on all public functions that are missing ddoc sections

[Kagamin via Digitalmars-d]

On Thursday, 19 March 2015 at 22:14:02 UTC, Jeremy Powers wrote:
>>     int foo;
>>     int getFoo() { return foo; }
>>
>
> A valid reason for doing things like this is future-proof 
> encapsulation.

That's a non-obvious property worth documenting. If it's a public 
API guaranteed to never change, that should be stated as such at 
least to warn against inconsiderate changes.