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.

Sign up for GitHub

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

Jump to bottom

Remove CompareAndSetOrdering trait and change compere_and_set to always use two orderings #621

Closed
taiki-e opened this issue Dec 24, 2020 · 0 comments · Fixed by #628
Closed

Remove CompareAndSetOrdering trait and change compere_and_set to always use two orderings #621

taiki-e opened this issue Dec 24, 2020 · 0 comments · Fixed by #628
Labels
breaking change crossbeam-epoch

Comments

@taiki-e
Copy link
Member

taiki-e commented Dec 24, 2020

Given that the standard library deprecated the methods that use a single ordering for CAS operation, I think it makes sense to remove CompareAndSetOrdering trait and change compere_and_set to always use two orderings.

Context: #620 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
breaking change crossbeam-epoch
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add Atomic::compare_exchange(_weak) and deprecate Atomic::compare_and_set(_weak) taiki-e/crossbeam
1 participant
@taiki-e