-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Standard Library Documentation Checklist #29329
Comments
…teveklabnik Add DirBuilder doc examples r? @steveklabnik Part of rust-lang#29329 and of rust-lang#29356.
…teveklabnik Add DirBuilder doc examples r? @steveklabnik Part of rust-lang#29329 and of rust-lang#29356.
@steveklabnik Looks like |
Suggestion: Turn this into a Project? (Might help in gaining visibility, or just to test if the workflow helps?) |
@critiqjo I like that idea! Is anybody against it? I would put one up but it seems that project creation is restricted. |
I think I went over every items. Once I have time, I'll try to check if I missed any. |
We haven't, as a matter of project policy, decided if we're using projects, and for what. We should talk about it at the next docs meeting. |
Opened an issue for moving to pulldown-cmark: #38400 |
Update: I'm going to go through all of the ones that are still open today and elaborate on exactly what they need to have done to be considered closed. |
…s, r=steveklabnik Improve the docs for the write and writeln macros This change reduces duplication by linking the documentation for `writeln!` to `write!`. It also restructures the `write!` documentation to read in a more logical manner (I hope; feedback would be welcome). Updates rust-lang#29329, rust-lang#29381
This change reduces duplication by linking the documentation for `writeln!` to `write!`. It also restructures the `write!` documentation to read in a more logical manner. Updates rust-lang#29329, rust-lang#29381
Update:
|
Unchecked
|
@steveklabnik update checklist please: |
Updated. |
I think this issue has served its use. There's only a few things left, and we can track them in their own issues. Thank you to everyone who pitched in and made the standard library docs better over the last three years! ❤️ |
I've been doing work on random parts of the standard library, but it's time to get systematic.
Here's a list of all of the top-level modules in
std
, with separate tracking issues for each part. Documentation is never done, but I'd at least like to ensure that every module is seen at least once.PRs will be sent for consistency, more examples, better explanations, all the usual stuff. But here's how we can track progress.
One specific area where we can do much better is linking of types to their docs in text explanations.
The text was updated successfully, but these errors were encountered: