Phobos Documentation - call to action

[Walter Bright via Digitalmars-d]

On 3/18/2015 10:55 AM, Zach the Mystic wrote:
> No responses yet -- not that I'm any less guilty than anyone else. But maybe
> this needs to be bumped up to a higher priority -- a hiatus on internal
> development for a couple weeks solely to bring documentation up to a minimum.
> Obviously clear guidelines like the ones you just posted are a plus.

We have a great language, but represent it poorly in the documentation. Every 
library entry also needs a pithy example (or even any example at all), but I 
thought we could make progress first by simply documenting what the return value 
is supposed to be.

We also need to stop pulling new library additions that have obviously 
inadequate documentation.