Use AtomicUsize from portable-atomic #23
Open
Conversation
This file contains 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
|
I didn't see #12 before writing this PR, still I think we should move forward with portable-atomic since atomic-polyfill is now deprecated |
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.
Use AtomicUsize from portable-atomic instead of core::sync::atomic, in order to support platforms where AtomicUsize is not natively supported (like for example my raspberry pi pico)
A link to https://github.com/taiki-e/portable-atomic?tab=readme-ov-file#optional-features should also be added to the README to instruct end users how to properly configure portable-atomic
P.S. Maybe the inclusion of portable-atomic should be behind a feature flag, but as I am learning Rust I am not sure what is the way to do it