Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
remote_code_oxidation is a project of mine that uses Rust to achieve reverse shells on a "victim" machine
intelligent_machine_discovery is a Rust-based discovery tool, that helps quickly find potential avenues for exploitation
Personally, I think that, if you're going that far into freeform prose documentation, it may be better to use mdBook and host it on GitHub Pages, like things like LALRPOP do.
(Just this week, someone expressed interest in volunteering to get things moving on supporting out-of-code Markdown files in cargo doc so you don't have to do as clap does and abuse Rust modules that only build when the code is being documented to achieve that... they also use constructs like #![doc = include_str!("../../examples/tutorial_derive/01_quick.md")] which may require nightly-channel Rust. I can't remember and don't have time to test it right now.)
Related posts
- How do I go about designing a CLI for which others can write extensions?
- Cargo Script
- Scriptisto: "Shebang interpreter" that enables writing scripts in compiled langs
- Shipp – Deadly simple package manager (for C/C++)
- Cargo has never frustrated me like npm or pip has. Does Cargo ever get frustrating? Does anyone ever find themselves in dependency hell?