default size of 4 is used for this. The size of the threadpool is controlled via environment variable UV_THREADPOOL_SIZE. While wai�ng for a free thread, and during func�on execu�on once a thread is available ccall to :uv_async_send, passing cond.handle as the argument, taking care to avoid any alloca�ons or other interac�ons with the Julia run�me. Note that events may be coalesced, so mul�ple calls to uv_async_send that wakes up tasks wai�ng for it (by calling wait on the object) when no�fied from C by a call to uv_async_send. Wai�ng tasks are woken with an error when the object is closed (by close. Use isopen to

default size of 4 is used for this. The size of the threadpool is controlled via environment variable UV_THREADPOOL_SIZE. While wai�ng for a free thread, and during func�on execu�on once a thread is available ccall to :uv_async_send, passing cond.handle as the argument, taking care to avoid any alloca�ons or other interac�ons with the Julia run�me. Note that events may be coalesced, so mul�ple calls to uv_async_send that wakes up tasks wai�ng for it (by calling wait on the object) when no�fied from C by a call to uv_async_send. Wai�ng tasks are woken with an error when the object is closed (by close. Use isopen to

default size of 4 is used for this. The size of the threadpool is controlled via environment variable UV_THREADPOOL_SIZE. While wai�ng for a free thread, and during func�on execu�on once a thread is available ccall to :uv_async_send, passing cond.handle as the argument, taking care to avoid any alloca�ons or other interac�ons with the Julia run�me. Note that events may be coalesced, so mul�ple calls to uv_async_send that wakes up tasks wai�ng for it (by calling wait on the object) when no�fied from C by a call to uv_async_send. Wai�ng tasks are woken with an error when the object is closed (by close. Use isopen to

default size of 4 is used for this. The size of the threadpool is controlled via environment variable UV_THREADPOOL_SIZE. While wai�ng for a free thread, and during func�on execu�on once a thread is available ccall to :uv_async_send, passing cond.handle as the argument, taking care to avoid any alloca�ons or other interac�ons with the Julia run�me. Note that events may be coalesced, so mul�ple calls to uv_async_send that wakes up tasks wai�ng for it (by calling wait on the object) when no�fied from C by a call to uv_async_send. Wai�ng tasks are woken with an error when the object is closed (by close. Use isopen to

default size of 4 is used for this. The size of the threadpool is controlled via environment variable UV_THREADPOOL_SIZE. While waiting for a free thread, and during function execution once a thread is available cond = Base.AsyncCondition() wait(cond) The callback you pass to C should only execute a ccall to :uv_async_send, passing cond.handle as the argument, taking care to avoid any allocations or other interactions 336 CHAPTER 34. CALLING C AND FORTRAN CODE Note that events may be coalesced, so multiple calls to uv_async_send may result in a single wakeup notifi- cation to the condition. 34.15 More About Callbacks

default size of 4 is used for this. The size of the threadpool is controlled via environment variable UV_THREADPOOL_SIZE. While wai�ng for a free thread, and during func�on execu�on once a thread is available ccall to :uv_async_send, passing cond.handle as the argument, taking care to avoid any alloca�ons or other interac�ons with the Julia run�me. Note that events may be coalesced, so mul�ple calls to uv_async_send that wakes up tasks wai�ng for it (by calling wait on the object) when no�fied from C by a call to uv_async_send. Wai�ng tasks are woken with an error when the object is closed (by close. Use isopen to

default size of 4 is used for this. The size of the threadpool is controlled via environment variable UV_THREADPOOL_SIZE. While waiting for a free thread, and during function execution once a thread is available cond = Base.AsyncCondition() wait(cond) The callback you pass to C should only execute a ccall to :uv_async_send, passing cond.handle as the argument, taking care to avoid any allocations or other interactions 318 CHAPTER 27. CALLING C AND FORTRAN CODE Note that events may be coalesced, so multiple calls to uv_async_send may result in a single wakeup notifi- cation to the condition. 27.15 More About Callbacks

default size of 4 is used for this. The size of the threadpool is controlled via environment variable UV_THREADPOOL_SIZE. While waiting for a free thread, and during function execution once a thread is available cond = Base.AsyncCondition() wait(cond) The callback you pass to C should only execute a ccall to :uv_async_send, passing cond.handle as the argument, taking care to avoid any allocations or other interactions interactions with the Julia runtime. Note that events may be coalesced, so multiple calls to uv_async_send may result in a single wakeup notifi- cation to the condition. 27.15 More About Callbacks For

default size of 4 is used for this. The size of the threadpool is controlled via environment variable UV_THREADPOOL_SIZE. While waiting for a free thread, and during function execution once a thread is available cond = Base.AsyncCondition() wait(cond) The callback you pass to C should only execute a ccall to :uv_async_send, passing cond.handle as the argument, taking care to avoid any allocations or other interactions interactions with the Julia runtime. Note that events may be coalesced, so multiple calls to uv_async_send may result in a single wakeup notifi- cation to the condition. 27.15 More About Callbacks For

default size of 4 is used for this. The size of the threadpool is controlled via environment variable UV_THREADPOOL_SIZE. While waiting for a free thread, and during function execution once a thread is available cond = Base.AsyncCondition() wait(cond) The callback you pass to C should only execute a ccall to :uv_async_send, passing cond.handle as the argument, taking care to avoid any allocations or other interactions interactions with the Julia runtime. Note that events may be coalesced, so multiple calls to uv_async_send may result in a single wakeup notifi- cation to the condition. 27.15 More About Callbacks For