fiber
fiber copied to clipboard
boostorg
userland threads
buffered_channel requests heap memory. In some simple scenarios this can be very inefficient. If a semaphore is provided, it can make it easier for its users to implement their own...
First of all, this is a very powerful library, regret having not met earlier follow the tutorial, start multiple threads, use condition variables to wait for finish. a strange thing...
This is the scheduling I implemented in QT, but it has issues and sometimes it won't be scheduled. Occasionally, I am confused and can't find where the problem lies ```...
We are in the process of making B2 build changes to all of the B2 build files to support "modular" consumption of the Boost Libraries by users. See this list...
Hello dear developers, This is more a quesion than a bug: When using fibers, the mutex provided by this library `fiber::mutex` is recommended because a _normal_ `std::mutex` does not know...
Hello! We are trying to package the Boost 1.84.0 on Conan but we are facing a linkage error related to the new `boost::fibers::make_stack_allocator_wrapper` introduced on [1.84.0](https://github.com/boostorg/fiber/compare/boost-1.83.0...boost-1.84.0) We have the follow...
I'm using fiber with shared_work algo on boost 1.78 aarch64. a simple code is ``` while (true)｛ this_fiber::sleep_for(100ms); ｝ ``` when system clock moves backwards, this fiber would never resumed.
I've been trying to hack up a way to wait for all fibers to complete, and I always end up with a count of 2 instead of 1 at the...
Fiber build script uses `` feature https://github.com/boostorg/fiber/blob/2cb72f5dcefdeffbb36636234e6ccb36282f8ae3/build/Jamfile.v2#L23-L26 which is defined in Context library build script. It works currently by pure luck that `boost-cpp.jam` (main Boost build script) was unintentionally consistently...
