Cargo.toml: sync profile with coreutils

[oech3]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.15%. Comparing base (3f5db7d) to head (3871c1f).
⚠️ Report is 34 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #69      +/-   ##
==========================================
+ Coverage   78.64%   85.15%   +6.51%     
==========================================
  Files          13       15       +2     
  Lines        2585     3490     +905     
  Branches      230      246      +16     
==========================================
+ Hits         2033     2972     +939     
+ Misses        552      517      -35     
- Partials        0        1       +1     

Flag	Coverage Δ
macos_latest	84.98% <ø> (+7.34%)	⬆️
ubuntu_latest	84.58% <ø> (+6.40%)	⬆️
windows_latest	17.33% <ø> (+2.63%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[codspeed-hq]

Merging this PR will improve performance by 11.9%

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

⚡ 2 improved benchmarks
✅ 18 untouched benchmarks
⏩ 9 skipped benchmarks¹

Performance Changes

	Mode	Benchmark	BASE	HEAD	Efficiency
⚡	Simulation	glass_pumpkin	9 µs	8.1 µs	+11.7%
⚡	Simulation	glass_pumpkin (BPSW)	9.1 µs	8.1 µs	+11.9%

---

_{Comparing oech3:patch-1 (dd1b4f3) with main (a71ea11)}

Footnotes

1. 9 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[xtqqczze]

num-prime is used not just by coreutils, could this be justified on it's own merits?

[oech3]

I guess optimization is applied for this crate when this is used by other projects missing profile.
It does not appear on the comment, but num-prime 's perf gained 6%.

[oech3]

It seems #69 (comment) is inccorrect. I'm not sure is i possible, but it might better to apply only for CodSpeed.

[xtqqczze]

This is a library crate, do optimization settings have any effect when used as a dependency?

[oech3]

I'm not sure. maybe, no. So this is useful only for benchmark.

[xtqqczze]

So this is useful only for benchmark.

Let's remove the comment referencing factor then, and take the performance improvement in benchmarks.

[oech3]

I'm not sure why is

num-prime (this crate)
bench/benches/bench.rs::benches::bench_prime_gen::prime generation (256 bits)
+6%
8.9 ms
8.4 ms

hidden from GitHub comment.

[xtqqczze]

---- primality::tests::lucas_mod_test stdout ----
thread 'primality::tests::lucas_mod_test' panicked at 'attempt to calculate the remainder with a divisor of zero', /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/core/src/ops/arith.rs:596:1
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

CI / cargo_test (1.70.0, ubuntu-latest) (pull_request)

[xtqqczze]

I'm not sure why is

num-prime (this crate)
bench/benches/bench.rs::benches::bench_prime_gen::prime generation (256 bits)
+6%
8.9 ms
8.4 ms

hidden from GitHub comment.

@sylvestre Does CodSpeed regression threshold need reconfiguration after 395cef5?