`ATOMIC_REF_*_LOCK_FREE` property macros
Open
@dsunder is already working on this.
Since Apr 30, 2018.
discussion
subject - atomic_ref (P0019)
- Dominant language
- HTML
- Stars
- 29
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
In the current paper, we have the following lockfree property macros:
// 3.� lock-free property
#define ATOMIC_REF_BOOL_LOCK_FREE unspecified
#define ATOMIC_REF_CHAR_LOCK_FREE unspecified
#define ATOMIC_REF_CHAR16_T_LOCK_FREE unspecified
#define ATOMIC_REF_CHAR32_T_LOCK_FREE unspecified
#define ATOMIC_REF_WCHAR_T_LOCK_FREE unspecified
#define ATOMIC_REF_SHORT_LOCK_FREE unspecified
#define ATOMIC_REF_INT_LOCK_FREE unspecified
#define ATOMIC_REF_LONG_LOCK_FREE unspecified
#define ATOMIC_REF_LLONG_LOCK_FREE unspecified
#define ATOMIC_REF_POINTER_LOCK_FREE unspecified
These appear to be similar to atomic<T>s lockfree property macros, which are designed to interoperate with C atomics.
I'm not sure that we need these for atomic_ref. What their role be? C++ users will determine lockfreeness via the member function/trait. Do we need these for C compatibility? Will C be able to interact/interoperate with atomic_ref?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.