Are Fibers just broken in D?

Byron Moxie bheads at moxiegroup.com
Fri Apr 20 18:58:36 UTC 2018


I am working on an application that makes heavy use of Fibers 
pools that are processed by a thread pool.

In WIN32 it looks like its leaking memory then it segfaults (I am 
guessing its an OOM).

I am also trying to use Semaphores and/or Conditions on shared 
data between fibers, which results in segfaults as well.

atomicLoad and atomicStore are not working either.

Are Fibers usable at all?  Cause it doesn't seem like.  I already 
re-arched this application to remove vibe.d (was fighting all 
sorts of sync and event errors)

This application is turning into my last straw for D..  I spend 
about 90% of my time fighting the compiler / library. I am really 
debating re-writing this application in c++ over the weekend (I 
have already lost money on this job after convincing by boss that 
D would be better).


More information about the Digitalmars-d-learn mailing list