-
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
std::fmt::Write
methods error documentation
#98861
Comments
@rustbot label +T-docs-rs +E-easy |
Hi, I've been looking into this and I can't find an actual implementation of the |
The implementors section shows that |
Would it be fair to have the docs say something along the lines of:
That way, it is clear that std doesn't produce any errors and also that the user should be aware that it is a possibility in third-party crates. |
It does: The internal implementation of This can be observed in user code by implementing a formatting trait which is then used with |
…triplett Adding more verbose documentation for `std::fmt::Write` Attempts to address rust-lang#98861
…triplett Adding more verbose documentation for `std::fmt::Write` Attempts to address rust-lang#98861
Hi everyone. This is a continuation of work on docs. And this is my first PR here. I will be grateful for any comments |
This continuation of work at rust-lang#98861
…cottmcm Added error documentation for write_fmt This continuation of work at rust-lang#98861
Is this still issue still open? |
I think we may close it since #105172 was merged. |
Location
std::fmt::Write
Summary
While opening this issue for Clippy, I noticed that many of the
write_xyz
methods have the following error description:While I understand that this is due to the description being general for any implementation, this can seem tautological to someone that's not familiar with these methods and I thought perhaps it'd make sense to expand this a bit and add common scenarios / scenarios implemented by the standard library.
write_fmt
seems to be missing this description in general.Thank you!
The text was updated successfully, but these errors were encountered: