Skip to content
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

impl Zeroable for Atomic* #157

Merged
merged 2 commits into from
Dec 21, 2022
Merged

Conversation

nolanderc
Copy link
Contributor

fixes #74

Added documentation for some feature flags on the `Zeroable` trait.
Also fixed some invalid references in doc-comments.
@Lokathor
Copy link
Owner

If I accept this as is it'll cause the same problem as happened before with #140, some platforms don't have atomics. However, the cfg to detect atomics is not available in 1.34 (the current MSRV).

So unfortunately this has to be behind a cargo feature. I guess we'd maybe call it zeroable_atomics?

@nolanderc
Copy link
Contributor Author

I see!

Pushed a new commit with the feature flag. Documented the feature (and the other feature flags in that module) on the trait.

Also, I saw that there was also some bad references in checked.rs, so I fixed these as well.

@Lokathor Lokathor merged commit a758c09 into Lokathor:main Dec 21, 2022
@Lokathor Lokathor added the semver-patch semver patch change label Jan 20, 2023
leod pushed a commit to leod/bytemuck that referenced this pull request Jun 3, 2023
* `impl Zeroable for Atomic*`

fixes Lokathor#74

* added feature flag for `zeroable_atomics`

Added documentation for some feature flags on the `Zeroable` trait.
Also fixed some invalid references in doc-comments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver-patch semver patch change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Zeroable should be implemented for Atomic*
2 participants