> unless uv_close() keeps track of currently outstanding requests and Libuv keeps track of all outstanding requests (how else would it have known who to notify for completion)
> how to cleanly shutdown a running event loop? Libuv is designed for use from nodejs, which runs the event loop until all workers are closed and requests handed. To shutdown cleanly, wait for all outstanding requests to complete and then close all handles. > What if during unwinding I will submit another request or try to open a new handle? You will have to decide how your application needs to handle this. > Same for uv_fs_t -- I can submit two write requests that will try to > update different locations in the same file. If these writes are > immediately "converted" to async/overlapped requests > Yes, there's a long-standing bug / PR that libuv sometimes assumes that fs writes simply can't fail: https://github.com/libuv/libuv/pull/269#discussion_r28131975 -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
