Skip to content

docs: where a comment goes, and when the code should say it instead - #712

Merged
lneto merged 1 commit into
masterfrom
claude_agents_comment_clarity
Aug 12, 2026
Merged

docs: where a comment goes, and when the code should say it instead#712
lneto merged 1 commit into
masterfrom
claude_agents_comment_clarity

Conversation

@lneto

@lneto lneto commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Two rules from the #693 review of a single comment.

An API-choice justification belongs on the line that makes the call, not floating above the signature; and before writing it, ask whether the call already carries the reason -- raw_cpu_ptr over this_cpu_ptr is its own comment to a kernel reader.

And reaching for a comment is first a signal to reconsider clarity: a better name, a named helper, a real enum. Comment what the code cannot be made to say.

@lneto
lneto force-pushed the claude_agents_comment_clarity branch from 288810e to 0acfae3 Compare August 12, 2026 14:06
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@lneto
lneto force-pushed the claude_agents_comment_clarity branch from 0acfae3 to 1db1e7f Compare August 12, 2026 14:08
@lneto
lneto merged commit 9fc5261 into master Aug 12, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant