Use AtomicUsize rather than AtomicU64 in CacheKey. - #70
Merged
dfrg merged 1 commit intoNov 7, 2024
Conversation
`AtomicU64` is unavailable on most 32-bit targets, but `AtomicUsize` is available most targets. It is exceedingly unlikely that there will be more `CacheKey`s than bytes in the process address space.
Collaborator
Author
dfrg
approved these changes
Nov 7, 2024
dfrg
left a comment
dfrg
left a comment
Owner
There was a problem hiding this comment.
LGTM, thanks for reducing the scope.
Merged
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
2 participants
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.
AtomicU64is unavailable on most 32-bit targets, butAtomicUsizeis available most targets.It is exceedingly unlikely that there will be more
CacheKeys than bytes in the process address space.