Lines Matching refs:napi_threadsafe_function

613 ### `napi_threadsafe_function`
6176 These APIs provide the type `napi_threadsafe_function` as well as APIs to
6184 Upon creation of a `napi_threadsafe_function` a `napi_finalize` callback can be
6218 creating the `napi_threadsafe_function`, and the next data pointer that was
6237 Threads can be added to and removed from a `napi_threadsafe_function` object
6244 `napi_threadsafe_function` objects are destroyed when every thread which uses
6248 `napi_threadsafe_function` is destroyed. `napi_release_threadsafe_function()`
6250 `napi_threadsafe_function`, because after the call completes, there is no
6251 guarantee that the `napi_threadsafe_function` is still allocated. For the same
6255 `napi_threadsafe_function` can be freed in its `napi_finalize` callback which
6261 Once the number of threads making use of a `napi_threadsafe_function` reaches
6317                                 napi_threadsafe_function* result);
6334   `napi_threadsafe_function` is being destroyed.
6336   `napi_threadsafe_function`.
6360 napi_get_threadsafe_function_context(napi_threadsafe_function func,
6387 napi_call_threadsafe_function(napi_threadsafe_function func,
6419 napi_acquire_threadsafe_function(napi_threadsafe_function func);
6441 napi_release_threadsafe_function(napi_threadsafe_function func,
6470 napi_ref_threadsafe_function(node_api_nogc_env env, napi_threadsafe_function func);
6496 napi_unref_threadsafe_function(node_api_nogc_env env, napi_threadsafe_function func);