So, from what I could compile from the source code of the boost.fiber library, it seems that it is really MORE more versatile and powerful than goroutines. The goroutines mantra should not share data between coroutines, but rather transfer data to them as needed. This, apparently, is possible both inside the fibers and with the channels ( boost::fibers::unbounded_channel<T>and boost::fibers::bounded_channel<T>), although I would like to keep in mind that the data is safely distributed between all the fibers in one stream. This is controlled (e.g. using mutexes) to provide only one fiber at a time, so you may not need channels for a particular use case.
, , . , , , . , Fiber (, ), . https://github.com/olk/boost-fiber/blob/master/examples/priority.cpp. , ,
, , , , , - , Fibers goroutine- , . , ( , ), ( , , ). , , -, - , .
, , , , Fibers, , , .