Agree with Eliot on all except this one:


> and to have to say [nil] instead of [].
>

because empty blocks are ambiguous with incomplete code.  That's why, if
nil is "supposed" to be the return value, I always explicitly specify it,
as I would any other value, and not an empty block.

If the return value isn't consumed, and I simply wish to "do nothing", then
I'll write a short comment like, "do nothing" to express the that
intention.  Leaving it empty could cause future readers to wonder whether
the code was ever finished, or not.

It fits in with why we format code across multiple, indented lines -- it's
not the most concise, but it is more literate.  Literacy is about
communicating well with readers, not necessarily always writing the
most-concise thing possible...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200225/8f7735e9/attachment.html>