Large codebases introduce challenges in governance, architecture, and security that require automated tooling beyond standard linters.
Procedural macros execute at compile-time but are limited because they operate on token streams without access to type information or a reflection API.
Rustdoc can output a versioned JSON representation of a crate's public API, providing a stable, machine-parsable format for building custom tools.
Explore tools like cargo-semver-checks, cargo-check-external-types, and the pavex framework that leverage Rustdoc JSON for tasks like versioning and dependency injection.
The format is not a silver bullet as it lacks function body information, but it represents a vital first step for building advanced meta-tooling for Rust.
Discussion covers how Rustdoc JSON integrates into the CI toolchain and the current inability to add custom metadata attributes for project-specific tooling.
Common pitfalls include linking data across crates, while future improvements may include stable identifiers, stabilization, and better multi-version support.
The book was created to bridge the gap between learning Rust syntax and building a complete, production-grade backend application.
55:29Mykhailo Maidan
1:00:08Stefan Baumgartner
50:43Rainer Stropek
31:20Marco Otte-Witte
13:14Francesco Ciulla
25:56Francesco Ciulla
30:10Patrick Koss
18:40Douglas Crockford
Jobs that call for the skills explored in this talk.
autoiXpert GmbH & Co. KG
Stuttgart, Germany
Sector Nord AG
Oldenburg, Germany
Peter Park System GmbH
München, Germany
doinstruct Software GmbH
Berlin, Germany
Detlev Louis Motorrad-Vertriebsgesellschaft
Hamburg, Germany
CONTIAMO GMBH
Berlin, Germany