P2689 R3 Atomic Refs Bound to Memory Orderings & Atomic Accessors

[wg21bot]

P2689R0 atomic_accessor (Christian Trott, Mark Hoemmen, Damien Lebrun-Grandie, Dan Sunderland)

[ogiroux]

Poll #1: We like the bound memory_order versions of atomic_ref
(This says nothing about whether these are aliases of general
a template that takes a memory_order argument.)
atomic_ref_relaxed
atomic_ref_acq_rel (acquire for load, release for store)
atomic_ref_seq_cst
SF F N A SA
1 11 0 1 0

Consensus

Poll #2:
X) The meaning of the bound memory_order is that is the default order
Y) The meaning of the bound memory_order is that is the only order
SX X N Y SY
1 1 3 4 2

Consensus for Y

SX : we have a variant of this type in Folly and it has been useful to be able to override this
SY : it's weird for atomic_ref_relaxed to have a seq_cst atomic done to it; since you can re-form the _ref you can still do it

Poll #3: the next version of this proposal, with these changes, should target SG1 & LEWG
atomic_accessor -> atomic_ref
atomic_accessor_relaxed -> atomic_ref_relaxed
atomic_accessor_acq_rel -> atomic_ref_acq_rel
atomic_accessor_seq_cst -> atomic_ref_seq_cst
(Return to SG1 for final wording when this is in LWG.)
SF F N A SA
6 6 2 0 0

[wg21bot]

P2689R1 atomic_accessor (Christian Trott, Mark Hoemmen, Damien Lebrun-Grandie, Dan Sunderland, Nevin Liber)