Skip to content

Mention more APIs in ParseIntError docs #143611

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

GrigorenkoPV
Copy link
Contributor

@GrigorenkoPV GrigorenkoPV commented Jul 7, 2025

Fixes #143602

r? @lolbinarycat

@rustbot label +A-docs

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools labels Jul 7, 2025
Copy link
Contributor

@lolbinarycat lolbinarycat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks mostly good to me, but I don't have reviewer permissions, so..

r? t-libs

@@ -45,8 +45,11 @@ impl From<!> for TryFromIntError {

/// An error which can be returned when parsing an integer.
///
/// This error is used as the error type for the `from_str_radix()` functions
/// on the primitive integer types, such as [`i8::from_str_radix`].
/// For example, this error is used in `from_str_radix()` functions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
/// For example, this error is used in `from_str_radix()` functions
/// For example, this error is returned by the `from_str_radix()` functions

nit

@rustbot rustbot assigned thomcc and unassigned lolbinarycat Jul 7, 2025
@ChrisDenton
Copy link
Member

Just as a general note, you should not usually r? an individual unless they explicitly asked for it (or you know they're the only person able to review). Even if someone with r+ permissions creates an issue, they may not have the bandwidth to review and someone else might be able and willing to. You can still @ them if you think it's important that they're aware.

/// on the primitive integer types, such as [`i8::from_str_radix`].
/// For example, this error is returned by the `from_str_radix()` functions
/// on the primitive integer types (such as [`i8::from_str_radix`])
/// and as the error type in their [`FromStr`] implementations.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
/// and as the error type in their [`FromStr`] implementations.
/// and is used as the error type in their [`FromStr`] implementations.

Just realized my change to the first half means the second half also needs to be rewritten in order to still make sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ParseIntError docs should mention other integer parsing functions
5 participants