Re: atomic operations compared to c++

2017-06-14 Thread gzp via Digitalmars-d
Actually I've just found an isue from 2015 (still in NEW state): https://issues.dlang.org/show_bug.cgi?id=15007 I've updated and linked this forum.

Re: atomic operations compared to c++

2017-06-14 Thread gzp via Digitalmars-d
I am fairly sure it isn't, but why is this needed if you use a parallelism oriented approach to the architecture and design? Sorry to repeat but whilst there are circumstances where this stuff is needed (operating systems), most other applications should be written without the need for locks,

Re: atomic operations compared to c++

2017-06-14 Thread gzp via Digitalmars-d
After digging into it the source for me it seems as D is lacking a "standardized" atomic library. It has some basic concepts, but far behind the c++ standards. I don't know if there are any RFC-s in this topic but it requires a lot of work. Just to mention some by my first experience: cas in

atomic operations compared to c++

2017-06-13 Thread gzp via Digitalmars-d
I'm trying to port some simple lock-free algorithm to D and as the docs are quite minimal I'm stuck a little bit. The memory order seem to be ok: MemoryOrder.acq -> C++ accquire MemoryOrder.rel -> C++ release MemoryOrder.raw -> C++ relaxed MemoryOrder.seq -> C++ seq_cst or acq_rel (the