4 ms·

Well, when I started learning (around Beta 2, I'm by no means an expert yet but eager to get there!) a lot of the docs about both I/O and type conversions/type

• steveklabnik 11y ago
  Oh, the "T" was confusing me, you mean the standard library docs? And yeah, there's certainly a ton of weak points. We landed a _lot_ of Rustdoc fixes that make certain things better, but there's still a ton more to write. I've been mostly focusing on the longform docs. I just wanted to make sure that I know where people are having problems, so I can know where to focus my efforts. Thanks.
  • verandaguy 11y ago
    Are there any ways the community can give back, and help work on the docs? A wiki maybe?
    • steveklabnik 11y ago
      The docs are all in-tree. I love community contributed docs, that's how I got started :) Just like any GitHub project, just send us a pull request!
    • lambda 11y ago
      Docs are maintained here: https://github.com/rust-lang/rust/tree/master/src/doc https://github.com/rust-lang/rust/tree/master/src/doc The book is in the "trpl" directory: https://github.com/rust-lang/rust/tree/master/src/doc/trpl https://github.com/rust-lang/rust/tree/master/src/doc/trpl The standard library docs are maintained in doc comments in the appropriate places in the source: https://github.com/rust-lang/rust/tree/master/src/libstd https://github.com/rust-lang/rust/tree/master/src/libstd You can clone the repository, modify it locally, and build and test the docs (yes, the docs get tested, most of the code samples are actually executable tests), or you can just edit them online in GitHub's editor and send a pull request that way if you're just making documentation suggestions that won't need any tests.