Linting with Dylint
summary
Dylint runs Rust lints loaded from user-specified dynamic libraries rather than a fixed set, and supplies a cargo-style CLI plus a linker trick that embeds the toolchain into library filenames so the right rustc driver loads. The demo lint TrioResult detects use of ? on an IO::Result when the enclosing function returns anyhow::Result and emits a warning suggesting added context; tests are UI comparisons of stderr. The repo works and a prototype attempts automated toolchain-upgrade fixes by replaying Clippy commits.
AI-written summary · about
chapters (11)
- 0:00Introduction to Dylint
- 1:18Rust linting overview
- 4:07How linting works
- 5:35Lint stages and types
- 7:25When to use Dylint
- 9:10Tools and workflow
- 12:49Example lint: try_io_result
- 17:46Testing custom lints
- 20:16Implementation details
- 25:08Resources and APIs
- 27:41Future work and closing
related talks
27mThe Wonderful World of Rust Tooling
25m"Compiler-Driven Development: Making Rust Work for You"
40mWe deserve helpful tools
27mBuilding Cross-Platform GUIs with Slint - A Practical Introduction
31mImproving Your Rust Life
01h 42mIntroduction to Rust (for people who have never used a compiler)
34mGood or Bad Vibes? Coding with AI in Rust
27mTeaching an IDE to understand Rust