Lines Matching refs:it
12 the result when it is done.
18 A notable aspect of libuv's thread facilities is that it is a self contained
36 wait for it to close using ``uv_thread_join()``.
50 implementation detail, avoid depending on it to always be true.
102 locked a mutex attempts to lock it again. For example, a construct like::
122 shared memory at the same time. A writer may not acquire the lock when it is
124 holding it. Read-write locks are frequently used in databases. Here is a toy
194 tempting is that it allows potentially any third-party libraries to be used
195 with the event-loop paradigm. When you use event loops, it is *imperative to
208 calculate fibonacci numbers, sleeping a bit along the way, but run it in
218 The actual task function is simple, nothing to show that it is going to be
220 arbitrary data through it using the ``void* data`` field and use it to
244 executing, or it has finished executing*, ``uv_cancel()`` **will fail**.
248 be scanned for audio files. If the user terminates the program, it should quit
311 with the async watcher whenever it receives a message.
317 thread, or it may be invoked after some time. libuv may also combine
322 or more calls, and libuv hasn't had a chance to run the callback yet, it
346 Finally it is important to remember to clean up the watcher.
389 it uses ``uv_async_send``.
