Search Results

I’m generally terrible at big-picture planning, so instead I’d like to talk about what I want to accomplish in the Rust world in 2018. Whether this slots into anyone else’s planning is another matter, but I’ll leave that as an exercise for the reader.

One of rustdoc’s greatest features is the ability to take code samples within your documentation and run them like tests. This ensures that all your samples stay up to date with your library’s API changes. However, there are some steps that need to happen to massage these “doctests” into something that can be compiled and run like a regular program.

Rustdoc has a pretty powerful feature that feels pretty unknown. It doesn’t help that it’s currently restricted by a nightly feature gate, but it’s still cool enough that I want to talk about it.

The “Increasing Rust’s Reach” projects are kicking off! With it, the Community Team is asking for people to describe how they contribute to Rust, to demonstrate the breadth of talent and perspective in the community. So here’s my personal Rust story!

A wishlist of what I would like to accomplish with Rust in 2019.

A recap of the 2019 Rust All-Hands from a rustdoc perspective; and the 2019 roadmap for the Rustdoc Team.

A companion to the RustConf 2019 talk with the same name; an introduction to making your first contribution to the Rust compiler.

Today we're announcing a brand new team: The Docs.rs Team!

To keep my usual long-windedness from obscuring the point of this post, i’ll put the summary up front: I’m stepping down from my positions as lead of the Docs.rs Team, and member of the Rustdoc and Documentation Teams, and ceasing my contributions for the immediate future. The Docs.rs Team will be co-led by Pietro Albini (@pietroalbini) and Joshua Nelson (@jyn514). The Rustdoc Team continues to be led by Guillaume Gomez (@GuillaumeGomez), and the Docs Team by Steve Klabnik (@steveklabnik).