## Why `argument-comment-lint` was green in CI even though the repo still had many uncommented literal arguments. The main gap was target coverage: the repo wrapper did not force Cargo to inspect test-only call sites, so examples like the `latest_session_lookup_params(true, ...)` tests in `codex-rs/tui_app_server/src/lib.rs` never entered the blocking CI path. This change cleans up the existing backlog, makes the default repo lint path cover all Cargo targets, and starts rolling that stricter CI enforcement out on the platform where it is currently validated. ## What changed - mechanically fixed existing `argument-comment-lint` violations across the `codex-rs` workspace, including tests, examples, and benches - updated `tools/argument-comment-lint/run-prebuilt-linter.sh` and `tools/argument-comment-lint/run.sh` so non-`--fix` runs default to `--all-targets` unless the caller explicitly narrows the target set - fixed both wrappers so forwarded cargo arguments after `--` are preserved with a single separator - documented the new default behavior in `tools/argument-comment-lint/README.md` - updated `rust-ci` so the macOS lint lane keeps the plain wrapper invocation and therefore enforces `--all-targets`, while Linux and Windows temporarily pass `-- --lib --bins` That temporary CI split keeps the stricter all-targets check where it is already cleaned up, while leaving room to finish the remaining Linux- and Windows-specific target-gated cleanup before enabling `--all-targets` on those runners. The Linux and Windows failures on the intermediate revision were caused by the wrapper forwarding bug, not by additional lint findings in those lanes. ## Validation - `bash -n tools/argument-comment-lint/run.sh` - `bash -n tools/argument-comment-lint/run-prebuilt-linter.sh` - shell-level wrapper forwarding check for `-- --lib --bins` - shell-level wrapper forwarding check for `-- --tests` - `just argument-comment-lint` - `cargo test` in `tools/argument-comment-lint` - `cargo test -p codex-terminal-detection` ## Follow-up - Clean up remaining Linux-only target-gated callsites, then switch the Linux lint lane back to the plain wrapper invocation. - Clean up remaining Windows-only target-gated callsites, then switch the Windows lint lane back to the plain wrapper invocation.
5.2 KiB
argument-comment-lint
Isolated Dylint library for enforcing
Rust argument comments in the exact /*param*/ shape.
Prefer self-documenting APIs over comment-heavy call sites when possible. If a
call site would otherwise read like foo(false) or bar(None), consider an
enum, named helper, newtype, or another idiomatic Rust API shape first, and
use an argument comment only when a smaller compatibility-preserving change is
more appropriate.
It provides two lints:
argument_comment_mismatch(warnby default): validates that a present/*param*/comment matches the resolved callee parameter name.uncommented_anonymous_literal_argument(allowby default): flags anonymous literal-like arguments such asNone,true,false, and numeric literals when they do not have a preceding/*param*/comment.
String and char literals are exempt because they are often already self-descriptive at the callsite.
Behavior
Given:
fn create_openai_url(base_url: Option<String>, retry_count: usize) -> String {
let _ = (base_url, retry_count);
String::new()
}
This is accepted:
create_openai_url(/*base_url*/ None, /*retry_count*/ 3);
This is warned on by argument_comment_mismatch:
create_openai_url(/*api_base*/ None, 3);
This is only warned on when uncommented_anonymous_literal_argument is enabled:
create_openai_url(None, 3);
Development
Install the required tooling once:
cargo install cargo-dylint dylint-link
rustup toolchain install nightly-2025-09-18 \
--component llvm-tools-preview \
--component rustc-dev \
--component rust-src
Run the lint crate tests:
cd tools/argument-comment-lint
cargo test
GitHub releases also publish a DotSlash file named
argument-comment-lint for macOS arm64, Linux arm64, Linux x64, and Windows
x64. The published package contains a small runner executable, a bundled
cargo-dylint, and the prebuilt lint library.
The package is not a full Rust toolchain. Running the prebuilt path still
requires the pinned nightly toolchain to be installed via rustup:
rustup toolchain install nightly-2025-09-18 \
--component llvm-tools-preview \
--component rustc-dev \
--component rust-src
The checked-in DotSlash file lives at tools/argument-comment-lint/argument-comment-lint.
run-prebuilt-linter.sh resolves that file via dotslash and is the path used by
just clippy, just argument-comment-lint, and the Rust CI job. The
source-build path remains available in run.sh for people
iterating on the lint crate itself.
The Unix archive layout is:
argument-comment-lint/
bin/
argument-comment-lint
cargo-dylint
lib/
libargument_comment_lint@nightly-2025-09-18-<target>.dylib|so
On Windows the same layout is published as a .zip, with .exe and .dll
filenames instead.
DotSlash resolves the package entrypoint to argument-comment-lint/bin/argument-comment-lint
(or .exe on Windows). That runner finds the sibling bundled cargo-dylint
binary and the single packaged Dylint library under lib/, normalizes the
host-qualified nightly filename to the plain nightly-2025-09-18 channel when
needed, and then invokes cargo-dylint dylint --lib-path <that-library> with
the repo's default DYLINT_RUSTFLAGS and CARGO_INCREMENTAL=0 settings.
The checked-in run-prebuilt-linter.sh wrapper uses the fetched package
contents directly so the current checked-in alpha artifact works the same way.
It also makes sure the rustup shims stay ahead of any direct toolchain
cargo binary on PATH, and sets RUSTUP_HOME from rustup show home when
the environment does not already provide it. That extra RUSTUP_HOME export is
required for the current Windows Dylint driver path.
If you are changing the lint crate itself, use the source-build wrapper:
./tools/argument-comment-lint/run.sh -p codex-core
Run the lint against codex-rs from the repo root:
./tools/argument-comment-lint/run-prebuilt-linter.sh -p codex-core
just argument-comment-lint -p codex-core
If no package selection is provided, run-prebuilt-linter.sh defaults to checking the
codex-rs workspace with --workspace --no-deps.
For non---fix runs, both wrappers also default the underlying Cargo
invocation to --all-targets unless you explicitly narrow the target set, so
workspace and package lint runs both cover test-only call sites by default.
Repo runs also promote uncommented_anonymous_literal_argument to an error by
default:
./tools/argument-comment-lint/run-prebuilt-linter.sh -p codex-core
The wrapper does that by setting DYLINT_RUSTFLAGS, and it leaves an explicit
existing setting alone. It also defaults CARGO_INCREMENTAL=0 unless you have
already set it, because the current nightly Dylint flow can otherwise hit a
rustc incremental compilation ICE locally. To override that behavior for an ad
hoc run:
DYLINT_RUSTFLAGS="-A uncommented-anonymous-literal-argument" \
CARGO_INCREMENTAL=1 \
./tools/argument-comment-lint/run.sh -p codex-core
To override an explicitly narrow target selection, or to be explicit in scripts:
./tools/argument-comment-lint/run-prebuilt-linter.sh -p codex-core -- --all-targets