OpenE2K/rust
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Direct contributors to try stage 0 rustdoc first

Browse Source
This commit is contained in:
Dylan MacKenzie 2020-04-28 08:55:41 -07:00
parent d7afaa7247
commit 23dbd33d93
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
CONTRIBUTING.md
View File

@ -393,10 +393,14 @@ You can find documentation style guidelines in [RFC 1574][rfc1574].
[rfc1574]: https://github.com/rust-lang/rfcs/blob/master/text/1574-more-api-documentation-conventions.md#appendix-a-full-conventions-text [rfc1574]: https://github.com/rust-lang/rfcs/blob/master/text/1574-more-api-documentation-conventions.md#appendix-a-full-conventions-text
In many cases, you don't need a full `./x.py doc`. You can use `rustdoc` directly In many cases, you don't need a full `./x.py doc`, which will build the entire
to check small fixes. For example, `rustdoc src/doc/reference.md` will render stage 2 compiler. When updating documentation for the standard library, first
reference to `doc/reference.html`. The CSS might be messed up, but you can try `./x.py doc --stage 0 src/libstd`. Results will should appear in
verify that the HTML is right. `build/$TARGET/crate-docs`.
You can also use `rustdoc` directly to check small fixes. For example,
`rustdoc src/doc/reference.md` will render reference to `doc/reference.html`.
The CSS might be messed up, but you can verify that the HTML is right.
Additionally, contributions to the [rustc-dev-guide] are always welcome. Contributions Additionally, contributions to the [rustc-dev-guide] are always welcome. Contributions
can be made directly at [the can be made directly at [the