# \[Accepted\] SE-0282: Interoperability with the C Atomic Operations Library **URL:** \ **Category:** Announcements\ **Created:** [June 30, 2020, 9:20pm UTC](https://forums.swift.org/t/accepted-se-0282-interoperability-with-the-c-atomic-operations-library/38050 "2020-06-30T21:20:12Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![Joe\_Groff](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/joe_groff/32/1929_2.png) [@Joe\_Groff](https://forums.swift.org/u/Joe_Groff)\ **Post date:** [June 30, 2020, 9:20pm UTC](https://forums.swift.org/t/accepted-se-0282-interoperability-with-the-c-atomic-operations-library/38050/1 "2020-06-30T21:20:12Z")
The review for [SE-0282: Interoperability with the C Atomic Operations Library](https://forums.swift.org/t/se-0282-review-2-interoperability-with-the-c-atomic-operations-library/37360/12) ran from June 8 to June 25. The core team has decided to **accept** this proposal. This revision, focused on interop with the C memory model, had more or less unanimous support. However, discussion revealed ambiguity about the interaction of Swift code with `memory_order_consume`. The following text will be added to the accepted proposal to clarify: This proposal does not specify whether/how dependency chains arising from the C/C++ `memory_order_consume` memory ordering work in Swift. The consume ordering as specified in the C/C++ standards is not implemented in any C/C++ compiler, and we join the current version of the C++ standard in encouraging Swift programmers not to use it. We expect to tackle the problem of efficient traversal of concurrent data structures in future proposals. Meanwhile, Swift programmers can start building useful concurrency constructs using relaxed, acquire/release, and sequentially consistent memory orderings imported from C. Thank you to everyone who participated in both rounds of review! --- _[View the full topic](https://forums.swift.org/t/accepted-se-0282-interoperability-with-the-c-atomic-operations-library/38050)._