# The Standard Library Documentation Checklist

**URL:** <https://internals.rust-lang.org/t/the-standard-library-documentation-checklist/2832>\
**Category:** libs\
**Created:** [October 26, 2015, 5:44pm UTC](https://internals.rust-lang.org/t/the-standard-library-documentation-checklist/2832 "2015-10-26T17:44:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![steveklabnik](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/steveklabnik/32/4524_2.png) [@steveklabnik](https://internals.rust-lang.org/u/steveklabnik)\
**Post date:** [October 26, 2015, 5:44pm UTC](https://internals.rust-lang.org/t/the-standard-library-documentation-checklist/2832/1 "2015-10-26T17:44:06Z")

</div>

Sorry for your inboxes. Now that I've accepted we'll have over 2k issues forever, open issues for all of the things:

[https://github.com/rust-lang/rust/issues/29329](https://github.com/rust-lang/rust/issues/29329)

I've been watching as the libs team has done something great for the last two cycles: choose a set of things to work on, and then come back to it at the end, making sure it all got done, or punting on things for later.

There isn't a 'docs team' yet, but I'm going to try to do the same thing, starting with 1.6. The 1.6 docs issue will be filed after we branch off 1.5, but here's a master checklist to make sure that we cover everything at least once before focusing on improving something that exists.

A lot of this already has a lot of good docs, I just want to make sure that we do the entire thing at least once. Lists are good for that.

---

<div class="post-metadata">

**Author:** ![steveklabnik](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/steveklabnik/32/4524_2.png) [@steveklabnik](https://internals.rust-lang.org/u/steveklabnik)\
**Post date:** [March 25, 2019, 8:25am UTC](https://internals.rust-lang.org/t/the-standard-library-documentation-checklist/2832/2 "2019-03-25T08:25:23Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
