Skip to content

chore(linux): check adding-drivers.md and drop repeated Cargo features - #3556

Merged
datlechin merged 2 commits into
mainfrom
chore/linux-docs-cargo-features
Oct 19, 2026
Merged

datlechin merged 2 commits into
mainfrom
chore/linux-docs-cargo-features

Conversation

@datlechin

Copy link
Copy Markdown
Member

Why

linux/docs/adding-drivers.md named three paths that do not exist (src/ddl.rs twice, tests/integration/main.rs), and the fast job's docs step never read it, so nothing caught them. Member manifests also listed tokio and tokio-util features the workspace entry already turns on, which reads as if each crate needed more than it gets.

Change

  • The three references now name real files, and the fast job's check-doc-symbols.sh step reads adding-drivers.md too.
  • Members list only features their workspace entry does not name; the driver template in the doc follows.

Verified

scripts/check-doc-symbols.sh over the fast job's list is clean. cargo tree -e features for every package, alone and with dev edges, plus the workspace and cargo metadata resolve features: 33,412 lines, identical before and after.

Not in this PR

  • error-handling.md, the five driver pages and linux/README.md still have 14 stale references between them and stay outside the check.

@datlechin
datlechin merged commit 64a8e4e into main Oct 19, 2026
24 checks passed
@datlechin
datlechin deleted the chore/linux-docs-cargo-features branch October 19, 2026 04:30
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