code review 11700043: present/dir.go: be more idiomatic when documenting bool...

present/dir.go: be more idiomatic when documenting boolean return values.
Phrases like "returns whether or not the image is opaque" could be
describing what the function does (it always returns, regardless of
the opacity) or what it returns (a boolean indicating the opacity).
Even when the "or not" is missing, the phrasing is bizarre.

Go with "reports whether", which is still clunky but at least makes
it clear we're talking about the return value.

[r, 2013-07-23 00:28:45]

Hello golang-dev@googlegroups.com,

I'd like you to review this change to
https://code.google.com/p/go.talks

[dsymonds, 2013-07-23 00:34:35]

LGTM

[r, 2013-07-23 00:37:18]

*** Submitted as
https://code.google.com/p/go/source/detail?r=0f2497c44599&repo=talks ***

present/dir.go: be more idiomatic when documenting boolean return values.
Phrases like "returns whether or not the image is opaque" could be
describing what the function does (it always returns, regardless of
the opacity) or what it returns (a boolean indicating the opacity).
Even when the "or not" is missing, the phrasing is bizarre.

Go with "reports whether", which is still clunky but at least makes
it clear we're talking about the return value.

R=golang-dev, dsymonds
CC=golang-dev
https://codereview.appspot.com/11700043