Update wording and fuzz test count

Author: tgross35

src/etc/test-float-parse/src/gen/exhaustive.rs

@@ -3,7 +3,8 @@ use std::ops::RangeInclusive;
 
 use crate::{Float, Generator, Int};
 
-/// Test every possible bit pattern. Not recommended for anything larger than `f32`!
+/// Test every possible bit pattern. This is infeasible to run on any float types larger than
+/// `f32` (which takes about an hour).
 pub struct Exhaustive<F: Float> {
     iter: RangeInclusive<F::Int>,
 }

src/etc/test-float-parse/src/lib.rs

@@ -31,8 +31,9 @@ mod gen {
     pub mod subnorm;
 }
 
-/// Fuzz iterations to run if not specified by CLI arg.
-pub const DEFAULT_FUZZ_COUNT: u64 = 100_000_000;
+/// Fuzz iterations to run if not specified by CLI arg. By default, test as many conditions
+/// as the `f32` exhaustive test.
+pub const DEFAULT_FUZZ_COUNT: u64 = u32::MAX as u64;
 
 /// If there are more tests than this threashold, the test will be defered until after all
 /// others run (so as to avoid thread pool starvation).