-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Remove incorrect information in Arguments docs. #16187
Conversation
The documentation deleted here all seems still up-to-date to me, it may need an example for clarification but it's true that the only way to safely create |
@@ -125,11 +125,6 @@ impl<'a> Arguments<'a> { | |||
/// and its arguments. This cannot be generated at runtime because it cannot | |||
/// safely be done so, so no constructors are given and the fields are private | |||
/// to prevent modification. | |||
/// | |||
/// The `format_args!` macro will safely create an instance of this structure | |||
/// and pass it to a user-supplied function. The macro validates the format |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This paragraph is fine, please reinstate it (I think you could revise it to say, e.g., "and pass it to a function or closures supplied as the first argument").
Ah, I misunderstood what the beef was. What about now? |
/// string at compile-time so usage of the `write` and `format` functions can | ||
/// be safely performed. | ||
/// and pass it to a function or closure, passed as the first argument. The | ||
/// macro validates the forma string at compile-time so usage of the `write` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
forma string
Looks good to me! |
Fixed the typo. |
Fixes #15830.