-
Notifications
You must be signed in to change notification settings - Fork 238
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
Removing saturating_add_assign and replacing with Saturating struct #4029
base: master
Are you sure you want to change the base?
Removing saturating_add_assign and replacing with Saturating struct #4029
Conversation
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.
Thank, LGTM! I applied the CI label but we'll also need to let someone from svm team take a look too
The CI has been failing in a check: https://buildkite.com/anza/agave/builds/15596#0193af2b-68f5-4b10-84d9-f316e42f9886 Would you mind fixing that? |
Resolved |
Clippy failure as well. Will grab that, and run locally from now on. |
In the future, the following are good command to run from the base of the repo:
The first two will keep the linters happy, the last one will ensure all test code can be compiled oto |
Clippy nightly has a bunch of errors right now that seem unrelated. Is there a set of rules that should be ignored? |
Are you sure you're using the correct nightly version ? If you use the one specified by
|
Thanks, I see the issue. I was using cargo +nightly, rather than ./cargo nightly |
e8672e5
to
195e81f
Compare
195e81f
to
d5bba54
Compare
As another note - when you make changes to the PR, please push them as new commits instead of squashing them down.
|
Problem
Cleaning up all usages of saturating add assign and replacing with Saturating
#502
Summary of Changes
Fixes #