Expand the Rust Bookshelf 📚

[frewsxcv]

In the Rust Documentation team meeting today, there was a discussion about bringing more books/docs into the Rust Bookshelf. We want to improve the discoverability for these other books and also provide Rust users with more non-introductory resources.

Here are some ideas:

• Learning Rust With Entirely Too Many Linked Lists
• The Rust FFI Omnibus
• The Little Book of Rust Macros
• The Embedded Rust Book
  • status: not yet written
• Rust API Guidelines
• Asynchronous Programming in Rust
  • status: work in progresss
• Rust Cookbook
• Rustc Guide
• Rust WebAssembly
  • status: work in progress

Note: this list is not exhaustive nor have any of these books been finalized as being added

cc @rust-lang/docs

[tinaun]

any chance of moving the rendered rfc repo http://rust-lang.github.io/rfcs/ to the bookshelf? or at least linking it in more places. i think it would be useful alongside the unstable book

[steveklabnik]

Triage: rustc guide has been added; embedded book has a PR open.

[jonas-schievink]

Triage: Embedded book is now added. Since the docs team has been disbanded, what do we do with this issue?

[GuillaumeGomez]

We keep it? The work hasn't been done yet after all.

[steveklabnik]

I'm of two minds. Like yes, we want to add these books to the bookshelf. But is this issue actually going to help that goal? I'm not sure.

Anyway, TL;DR is that yes, we'd still like to do this and it's not done yet.

[pnkfelix]

Visiting for T-compiler backlog bonanza.

This doesn't have a clear owner, either as a person nor as a team. The compiler team does not believe it to be a tracking issue in the usual sense.

I am for now assigning it to T-lang, under the philosophy that they are closest to making decisions about how people using Rust interface with it. But I would be fine with it being bounced to T-core, or to any other team that is currently active.

@rustbot label: T-lang I-lang-nominated

[joshtriplett]

We discussed this in today's @rust-lang/lang meeting.

An omnibus issue with a variety of items in it is hard to make progress on. We're going to close this issue, however, we'd like to add links to the items in this list that are official (under the rust-lang organization): the API guidelines, and (if the team maintaining it thinks it's ready for this) the async programming guide.

We could also link to the RFCs guide, with appropriate caveats for what it means and that it isn't necessarily up-to-date documentation (e.g. we update features without going back and updating the RFC).

We're not at this time looking to link to further third-party resources from this page.