<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 4 July 2015 at 10:39, rsw0x via Digitalmars-d <span dir="ltr"><<a href="mailto:digitalmars-d@puremagic.com" target="_blank">digitalmars-d@puremagic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">On Saturday, 4 July 2015 at 07:16:09 UTC, Iain Buclaw wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">
On 4 Jul 2015 00:50, "rsw0x via Digitalmars-d" <<a href="mailto:digitalmars-d@puremagic.com" target="_blank">digitalmars-d@puremagic.com</a>> wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
[...]<br>
</blockquote></blockquote><span class="">
__sync_* builtins to the new (more compatible with how core.atomics is supposed to function) __atomic_* builtins.<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
[...]<br>
</blockquote></blockquote><span class="">
accepted as valid, but makes no sense.<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
[...]<br>
</blockquote></blockquote><span class="">
both cases to throw a compilation error (using static assert).  However I'd like the core druntime team to be on board with this.<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
[...]<br>
</blockquote><span class="">
forgot until I read this.<br>
<br></span>
[...]<br>
</blockquote>
<br>
This is how it's currently implemented in C++ as of C++14, correct?<br>
acquire semantics on a write and release semantics on a load make no sense, so this probably should be changed.<br>
</blockquote></div><br><br>Yes, that is correct.  I think closely matching the behaviour of C++14 
is the safe option given that this module shares a lot in common with std::atomic.<br><br>std::atomic::atomic_compare_exchange_strong -> core.atomic.cas<br></div><div class="gmail_extra">std::atomic::memory_order -> core.atomic.MemoryOrder<br></div><div class="gmail_extra">std::atomic::atomic_load -> core.atomic.atomicLoad<br></div><div class="gmail_extra">std::atomic::atomic_store -> core.atomic.atomicStore<br></div><div class="gmail_extra">std::atomic::atomic_thread_fence -> core.atomic.atomicFence<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Iain.<br></div><div class="gmail_extra"><br><br><span class=""><span><span class=""></span></span></span></div></div>