Skip to content

Fix sort for RangeCumSum #210

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

Merged
merged 2 commits into from
Mar 20, 2024
Merged

Fix sort for RangeCumSum #210

merged 2 commits into from
Mar 20, 2024

Conversation

jishnub
Copy link
Member

@jishnub jishnub commented Mar 19, 2024

The in-place sort should only be defined for Base.OneTo cumsums, as otherwise we can't guarantee an increasing result.

Copy link

codecov bot commented Mar 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.67%. Comparing base (25a5160) to head (da5e1dc).
Report is 2 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master     #210       +/-   ##
===========================================
+ Coverage    0.00%   89.67%   +89.67%     
===========================================
  Files          11       11               
  Lines        1736     1841      +105     
===========================================
+ Hits            0     1651     +1651     
+ Misses       1736      190     -1546     

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

@jishnub jishnub merged commit 8d81d29 into master Mar 20, 2024
17 checks passed
@jishnub jishnub deleted the jishnub/sortrangecumsum branch March 20, 2024 03:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant