Repository navigation
Clarify nested-call exemptions and bare-name if() conditions - #18
Conversation
The exemption list for arguments an outer function captures itself read as possibly closed. State that the capture test decides the exemption and the listed cases are examples, and that an argument evaluated as an ordinary value is never exempt. The bare-name rule for if()/while() conditions already covered conditions with no nested call; name a single comparison like `x > 0` explicitly so nobody reads it as an exception. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CVcpP4PWwqXdXBQtQF5JeK
Address review: replace the ambiguous 'That test' with the criterion, and give a concrete non-exempt case (an inner call inside all_of()). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CVcpP4PWwqXdXBQtQF5JeK
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Address the review's optional note: the test restated the clause it followed. Fold the not-a-closed-list point into that clause. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CVcpP4PWwqXdXBQtQF5JeK
|
Posted by Claude Code (AI agent) --- not written by a human. Generated by Claude Code |
|
Claude finished review — View run Review: #18Range reviewed: What changedThis commit addresses, almost verbatim, the only non-blocking note from the prior review (commit
into one:
( Checks
This is a pure prose tightening with no new content, consistent with and fully resolving the only open note from the prior review (2026-10-12T09:40:21Z), whose verdict (Ready for merge) still stands and is now reinforced by this follow-up cleanup. VerdictReady for merge Structured Review Data (JSON){
"schema_version": "1.1",
"reviewer": "claude",
"commit_sha": "958c5d33df3e6eea044518656065c62b1460da1f",
"verdict": "CLEAN",
"findings": [],
"detailed_assessment": "chapters/coding-style/avoid-nesting.qmd lines 19-20 collapse two redundant sentences into one without changing meaning, removing the circularity noted in the prior review round.",
"holistic_assessment": "Scope stays limited to the single prose file, no workflow or dependency or bibliography or build-artifact changes, and the fix matches the suggestion from the previous validated review."
}Reviewed commit: a49c0e9 |
2026-10-12 21:38 UTC |
Before:
avoid-nesting.qmdlisted the arguments exempt from the nested-call rule (tidyselect helpers, data-masked expressions,aes(), formulas) without saying whether the list was closed. It also saidif()conditions are "always a bare name", without saying whether that covers a plain comparison likeif (x > 0).After: the page says the test (does the outer function capture and interpret the argument?) decides the exemption, and the listed cases are examples. A worked case,
select(df, all_of(names(x))), shows that the exemption stops at the captured argument. A single comparison likex > 0is named as still needing a named condition.How: two prose edits to
chapters/coding-style/avoid-nesting.qmd. They settle the two open scope questions left after psc#15. Ezra handed both decisions over withdaytb.🤖 Generated with Claude Code
https://claude.ai/code/session_01CVcpP4PWwqXdXBQtQF5JeK
Generated by Claude Code