-
Notifications
You must be signed in to change notification settings - Fork 77
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
fix: (csl) Use u32
as the counter in async loops
#3353
Conversation
Previously, `i16` was used, this significantly limited the maximum loop iterations.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3353 +/- ##
=======================================
Coverage ? 90.09%
=======================================
Files ? 447
Lines ? 56578
Branches ? 5431
=======================================
Hits ? 50975
Misses ? 4166
Partials ? 1437 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but do we need that many iterations? What is the max number of iterations we intend to run, and could this be modelled with a u16
?
The runtime I get when running for ~30000 iterations is extremely low, on the order of 10ms, having the ability to bump it higher would let us do longer runs. Is there any benefit to |
Would you expect there to be any performance implications? |
Not from reading the docs, no. |
Previously, `i16` was used, this significantly limited the maximum loop iterations.
Previously,
i16
was used, this significantly limited the maximum loop iterations.