Fix an off by 1 error in test-float-parse

[speedy-lex]

    SUCCESS for generator 'f64 large integer values'. 59508/59508 passed in 1.2150712s
    SUCCESS for generator 'f16 exhaustive'. 65536/65536 passed in 3.148837s
      warning: executed tests != estimated (65536 != 65535) for exhaustive <<<< This is what is fixed
    SUCCESS for generator 'f32 fuzz'. 65535/65535 passed in 1.5524527s
    SUCCESS for generator 'f64 few ones int'. 262144/262144 passed in 1.2051041s

[rustbot]

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[jieyouxu]

r? @tgross35

[tgross35]

The title had me worried for a minute, but this is in the total estimation :) thanks!

@birs r+ rollup

[speedy-lex]

@tgross35, I'm pretty sure you meant to ping @bors

[tgross35]

Whoop, sorry about that birs.

@bors r+ rollup

[bors]

📌 Commit 0f52ff8 has been approved by tgross35

It is now in the queue for this repository.

[bors]

🌲 The tree is currently closed for pull requests below priority 102. This pull request will be tested once the tree is reopened.

[tgross35]

Oh, there is a conflict because I guess I also fixed this in #137525.

@bors r-

[bors]

☔ The latest upstream changes (presumably #137927) made this pull request unmergeable. Please resolve the merge conflicts.

[speedy-lex]

@tgross35, I feel like this solution is better as it can't panic. I don't think an estimation should panic.

[tgross35]

I think it's actually preferable to panic here - that limit is only hit if attempting to run exhaustive tests on f64 or f128, I'd rather be notified immediately then coming back a few hours later and realizing I started a test that will run for the next 2159123 years :) (I just tried it to get that estimate)

[rustbot]

There are merge commits (commits with multiple parents) in your changes. We have a no merge policy so these commits will need to be removed for this pull request to be merged.

You can start a rebase with the following commands:

$ # rebase
$ git pull --rebase https://github.com/rust-lang/rust.git master
$ git push --force-with-lease

The following commits are merge commits:

• 54a791d