Ihor Radchenko <[email protected]> writes: > While I do not object this particular change, do note that explicit cond > clause is not always bad. Sometimes, it is used for clarity - if the nil > return value is intended as a part of function spec. > > Of course, clarity is always subjective, but, sometimes, making the > intention clear is important, even if the code is redundant.
Agreed in general. In this particular case, however, the explicit clause emphasizes that `cond' returns nil, suggesting that this return value matters to the surrounding code, while the value is actually discarded. Thus, rather than clarifying the intent, the clause was potentially misleading. Best, -- Slawomir Grochowski
