On 2016-03-06 10:05, Dmitry Olshansky wrote:
However the opposite is also bad - in D you need to re-implement ALL of network/IO libraries from scratch to use async+fibers like e.g. vibe.d. Our famous C/C++ interop actually hurts us in this case because it's TRIVIAL to stumble on a blocking call in a fiber via some 3rd party library.
I'm wondering how much work it would be to expose the read/write functions from vibe.d, update a C library to use the read/write functions from vibe.d and use that C library together with vibe.d.
-- /Jacob Carlborg
