Diff Detail
Diff Detail
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 26691 Build 25055: arc lint + arc unit
Event Timeline
Comment Actions
I was told by bde (?) that after the block of code that is described by the multi-line comment, there should be a blank line. Since you carefully document other moments, this one should be described as well, I believe.
Comment Actions
I don't know if this update is a hard and fast style rule, but it makes sense to me in contexts like the written example. IMO, people shouldn't take it too literally — for example, if the code described is at the end of a block using }, you don't necessarily need a blank line to delineate scope, because the } line ends the scope neatly.
(If your block is a single statement and lacks {/}, and has a multi-line comment, maybe it should add {/} rather than a blank line. I don't feel the need to codify that in style.9.)