Best practices for reading public interfaces

[anonymous via Digitalmars-d-learn]

On Saturday, 21 February 2015 at 20:46:09 UTC, Kenny wrote:
> b) Write DDocs and read documentation. The problem here is that
> I'm going to use D only for my own projects and in the last time
> I tend to write less documentation, for example I do not write 
> it
> for the most methods of Vector3D.

If you're only interested in the signatures, empty documentation 
comments give you that.