Skip to content

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

@taiki-e

Description

@taiki-e

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)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions