-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Make cfg_has_atomic_x
public
#133
Comments
Thanks for the request. I'm open to making them public, but I have one question.
At first glance, your use case seems to always require AtomicU64, why have you disabled the enabled by default |
It's more in the line of : my function can receive any atomic integer. And I'm trying to model this by introducing a trait for it. So I don't "require all atomics", instead I would like to "support all existing atomics". |
Your code used fetch_add (which is not available in thumbv6m by default), so I was wondering if you enabled critical-section or single-core related features, otherwise AtomicU64 is indeed not provided even with fallback feature enabled. |
Thanks <3 |
Published in 1.6.0. |
Quote from the library:
Rationale
I have a library crate that wants to
The problem is that one of the target architectures does not support AtomicU64 by default, and as a lib I shouldn't enable any features of
portable-atomic
. So I get the compiler error thatAtomicU64
does not exist.I need a
cfg
detection of whether or not a specific atomic exists, so I can disableimpl
s for unavailable atomic types.The text was updated successfully, but these errors were encountered: