docs: sharpen the usage-rs pitch and cross-link framework completions - #1307
docs: sharpen the usage-rs pitch and cross-link framework completions#1307jdx wants to merge 3 commits into
Conversation
Lead with the framework and its two headline claims — feature coverage against clap and parser speed — then say where the speed comes from. Co-authored-by: jdx <jdx@users.noreply.github.com>
State the measured standing and the compile-time reason for it, and drop the cold-metadata sentence the sections below already cover. Co-authored-by: jdx <jdx@users.noreply.github.com>
usage-rs and usage-go ship completions from compiled tables, so send those readers to the framework pages before the spec-driven workflow. Co-authored-by: jdx <jdx@users.noreply.github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThe documentation distinguishes framework-generated and CLI-generated completions. It also updates Rust framework positioning and parser performance descriptions with compile-time table details and measured comparisons. ChangesCLI completion guidance
Rust framework documentation
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This PR makes localized documentation and cross-linking updates with no actionable merge-blocking risk remaining after normal checks and review. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Instruction counts
No instruction-count regression above 1%. Only instruction counts gate. Wall clock is shown for context — on identical hardware it moves 4-20% run to run. Measured by tak — instruction-counted CLI benchmarks, stored in this repository's git notes. Shadow comparisonParsing
|
Three copy changes, one per commit.
/rust/openingOpened with what
usage-rsis rather than how it works: a CLI framework for Rust applications and the reference implementation of the usage spec, fully featured against clap, with a parser up to thousands of times faster. The mechanics (structs and enums, clap-compatible derive spellings) moved into the second paragraph, and the speed claim now says where the speed comes from — static tables laid out at compile time instead of a parser built and validated on every run.Numbers are the ones the gate measures: 855x fewer instructions than clap, 2,957x fewer than bpaf, 1.3 MB stripped against clap's 3.1 MB.
/rust/performanceopeningLeads with the measured standing and the compile-time reason for it. Dropped the "Cold metadata for help, specs, and completions is not constructed on a successful parse" sentence — Why it is fast already covers it in context.
/cli/completionscalloutReaders building with
usage-rsorusage-gowere landing on the spec-driven CLI workflow. A tip at the top sends them to the framework pages and notes that those binaries answer completions from compiled tables, with no spec file to ship and nousageruntime dependency for their users.Verification
Built the site and read the rendered pages.
Rust framework landing page with the new opening
Parser performance page leading with the measured result
Completion scripts page with the new framework callout
To show artifacts inline, enable in settings.
Summary by CodeRabbit
usageCLI.