Merged
Conversation
This decrements the uint64 var like documentation states it, see https://pkg.go.dev/sync/atomic#AddUint64
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This decrements the uint64 var in Gauge as per go.dev documentation, see https://pkg.go.dev/sync/atomic#AddUint64 .
Without this change a bunch of unit tests are failing on my ARM-based Mac.
My best guess as to why
atomic.AddUint64(&m.value, toUint64(-value, 2))had worked before is thattoUint64(-value, 2)produces the same result as^uint64(toUint64(value, 2)-1)on some CPU architectures.Alternative to this change one may also consider the "less error-prone"
Uint64.Addfunction (according to documentation) that has been added to atomic in the meantime.Type of change
Testing performed?
Checklist:
mainbranch, or relevant version branch