Skip to content
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

Add a potential cause raising ParseIntError. #48738

Merged
merged 4 commits into from
Mar 9, 2018

Commits on Mar 4, 2018

  1. Add a potential cause raising ParseIntError.

    Initially, I wanted to add it directly to the documentation of `str. parse()' method, I finally found that it was more relevant (I hope so?) to directly document the structure in question. I've added a scenario, in which we could all get caught at least once, to make it easier to diagnose the problem when parsing integers.
    Songbird0 committed Mar 4, 2018
    Configuration menu
    Copy the full SHA
    c68440c View commit details
    Browse the repository at this point in the history
  2. Tidy error: add a new line

    The error was:
    
    ```
    [00:05:25] tidy error: /checkout/src/libcore/num/mod.rs:3848: trailing whitespace
    [00:05:25] tidy error: /checkout/src/libcore/num/mod.rs:3851: line longer than 100 chars
    [00:05:25] tidy error: /checkout/src/libcore/num/mod.rs:3851: trailing whitespace
    [00:05:26] some tidy checks failed
    ```
    The line was truncated to 92 characters.
    Songbird0 committed Mar 4, 2018
    Configuration menu
    Copy the full SHA
    247fc38 View commit details
    Browse the repository at this point in the history

Commits on Mar 5, 2018

  1. Configuration menu
    Copy the full SHA
    ef1aae1 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    6d71aa4 View commit details
    Browse the repository at this point in the history