Sid
Sid
wait in hope Thank you for your response
是的, 一共有两个超时判定 io loop的timeout和ev->timeout 分层来看 io loop只关心io和timer综合后应当timeout的值 event只关心上层给的timeout和自己的timeout谁更小 整体来看 所以io loop提供的timeout只是一个建议的值 event_process会把两个timeout做比较, 用最小的那个 你所说的动态修改是指ev->timeout吧, 看到poll和fiber delay会改它 又review了一遍代码, 应该没啥问题?
```C unsigned acl_fiber_nready(void) { if (__thread_fiber == NULL) { return 0; } return (unsigned) ring_size(&__thread_fiber->ready); } ``` 是根据ndead仿照的, 是否有遗漏的情况呢
or set cencel callback eg. ```lua effil.set_cancel_callback(function() -- cleanup code end) -- logic code ```
hope it still can be come out
i see ``uv_write2`` to send handle but it is an async op in my project, i make a wrapper interface for libuv, which have a option to decide the IO...
Thanks for the follow-up. > **Why do you need it to be sync?** > **You could likely synchronize it with a condition variable you wait on when the handle is...
when CMAKE_DEBUG_POSTFIX was set, the dll name is ``plainlua_d.dll`` not ``plainlua.dll`` if build type not debug, the expr is empty