We have a common pattern in the code base where we use the WT_PUBLISH macro

#define WT_PUBLISH(v, val)  \
    do {                    \
        WT_WRITE_BARRIER(); \
        (v) = (val);        \
    } while (0) 

for enforcing both read_once and ordering semantics. We've been discussing in the review committee meetings whether it makes sense to split these out into separate macros and how this will impact ease of code writing/reading.

We'll create a small proof of concept that show the usage of these new macros to see how readable it is and if it's worth pursuing further.