mvriel/Docblox — comment on commit 589ebad154ba881b6998425d81eaf677023a5b3c
File: docs/PSR.md line 514
By GaryJones:

> I think the far more general case is of a method that is meant to not return anything, and therefore I'd want my API doc to tell the reader that the method is of the "return void" variety.

But it can do that, by not including any `@return` tag within the DocBlock at all - this lets documentation generators to fallback and populate it with `void` if they want. For coders looking directly at the code, they can *see* that there's no `return` called by a) there being no `return` call, and b) there being no `@return` tag.

What you're implying is that you want to duplicate something that is already known, and do it in such a way that it's against what the PHP docs say. I could assign `a()` above to a variable, and that variable would === `Null`, yet according to the docs you want to impose, it would have a value of `void` - you're expecting developers to *know* that in reality it's going to be Null, instead of using the documentation to either state it is null (for `b()` and `c()`) or simply not including the tag (for `a()`).

Quite simply, if there's no 'return' call, don't include a `@return' tag - that follows the practices that people have been following, is more *accurate* than than giving it as void, and reduces the lines of redundant commentary.