-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
API Docs: fmt #29355
Comments
Doc improvement on std::fmt module Part of rust-lang#29355. r? @steveklabnik
Doc improvement on std::fmt module Part of rust-lang#29355. r? @steveklabnik
Doc improvement on std::fmt module Part of rust-lang#29355. r? @steveklabnik
Doc improvement on std::fmt module Part of rust-lang#29355. r? @steveklabnik
Doc improvement on std::fmt module Part of rust-lang#29355. r? @steveklabnik
Doc improvement on std::fmt module Part of rust-lang#29355. r? @steveklabnik
Doc improvement on std::fmt module Part of rust-lang#29355. r? @steveklabnik
Doc improvement on std::fmt module Part of rust-lang#29355. r? @steveklabnik
Doc improvement on std::fmt module Part of rust-lang#29355. r? @steveklabnik
Doc improvement on std::fmt module Part of rust-lang#29355. r? @steveklabnik
I am happy to mentor anyone who wants to tackle this issue. |
@steveklabnik, I would like to work on this. |
@webbm awesome, please let me know if you need anything. |
Hi @webbm! Before I start working on some of the items on the checklist I wanted to check with you to see which items are still available so that we don't duplicate effort. |
@mandeep, I have done a little of 1, 2, 4, and 5 is in progress. I'm going to create a Trello board to keep track of my own progress. Should I add all these as tasks and add you? |
@webbm No need for Trello just yet. I'll work on item 3 this weekend and report back. |
@steveklabnik If no one is looking at this I'll jump in for |
@rthomas I'm not aware of any active work right now, that'd be great! |
This rewords and removes the `Arguments` section from the docs for fmt::format. r? @steveklabnik
I have sent PRs for |
Looking at the last one ( |
Update docs for fmt::write. rust-lang#29355 I reworded it slightly to make it more clear that the function only take two arguments - the output and the Arguments struct that can be generated from the format_args! macro. r? @steveklabnik
Update docs for std::fmt::format rust-lang#29355. This rewords and removes the `Arguments` section from the docs for fmt::format. r? @steveklabnik
Update docs for fmt::write. rust-lang#29355 I reworded it slightly to make it more clear that the function only take two arguments - the output and the Arguments struct that can be generated from the format_args! macro. r? @steveklabnik
Update docs for std::fmt::format rust-lang#29355. This rewords and removes the `Arguments` section from the docs for fmt::format. r? @steveklabnik
Update docs for fmt::write. rust-lang#29355 I reworded it slightly to make it more clear that the function only take two arguments - the output and the Arguments struct that can be generated from the format_args! macro. r? @steveklabnik
Update docs for std::fmt::format rust-lang#29355. This rewords and removes the `Arguments` section from the docs for fmt::format. r? @steveklabnik
This adds docs for the Debug* structs as well as examples from the Formatter::debug_* methods, so that a user knows how to construct them. I added these examples as the builders module is not public and hence the debug_*_new() functions are not available to a user. r? @steveklabnik Review comments. Mainly adding in the links for all of the structs and functions. Remove rust tag on code blocks.
Update docs for Debug* structs. rust-lang#29355 This adds docs for the Debug* structs as well as examples from the Formatter::debug_* methods, so that a user knows how to construct them. I added these examples as the builders module is not public and hence the debug_*_new() functions are not available to a user. r? @steveklabnik
This adds a pretty contrived example of the usage of fmt::Error. I am very open to suggestions for a better one. I have also highlighted the fmt::Error vs std::error::Error. r? @steveklabnik
Update docs on Error struct. rust-lang#29355 This adds a pretty contrived example of the usage of fmt::Error. I am very open to suggestions for a better one. I have also highlighted the fmt::Error vs std::error::Error. r? @steveklabnik
…, r=steveklabnik Update trait summaries for std::fmt This patch is part of rust-lang#29355. r? @steveklabnik
+1 |
I'm going to send in a PR to help |
Part of #29329
http://doc.rust-lang.org/std/fmt/
Here's what needs to be done to close out this issue:
C
formatting", whereC
is the char, rather than their current boilerplate. Except Write. And Display.fmt::Result
needs an example, showing off theuse std::fmt; fmt::Result
pattern.write
should have itsArguments
section removed, we don't do this.format
has the same issue, and needs more explanation generally.Write
needs a lot of links. and some examples.Arguments
needs examples, but also a justification of why this is all done this way.DebugList
should use the iterator boilerplate language, even though it's not an iterator. Mostly pointing to the docs of the function that creates it.DebugMap
same.DebugSet
same.DebugStruct
same.DebugTuple
same.Error
needs examples, and specificallyuse std::fmt; fmt::Error
Formatter
should show where it's created, and talk about the details more.The text was updated successfully, but these errors were encountered: