@@ -284,16 +284,12 @@ This is an opaque pointer that is used to represent a JavaScript value.
284
284
285
285
### napi_threadsafe_function
286
286
287
- > Stability: 2 - Stable
288
-
289
287
This is an opaque pointer that represents a JavaScript function which can be
290
288
called asynchronously from multiple threads via
291
289
`napi_call_threadsafe_function()`.
292
290
293
291
### napi_threadsafe_function_release_mode
294
292
295
- > Stability: 2 - Stable
296
-
297
293
A value to be given to `napi_release_threadsafe_function()` to indicate whether
298
294
the thread-safe function is to be closed immediately (`napi_tsfn_abort`) or
299
295
merely released (`napi_tsfn_release`) and thus available for subsequent use via
@@ -307,8 +303,6 @@ typedef enum {
307
303
308
304
### napi_threadsafe_function_call_mode
309
305
310
- > Stability: 2 - Stable
311
-
312
306
A value to be given to `napi_call_threadsafe_function()` to indicate whether
313
307
the call should block whenever the queue associated with the thread-safe
314
308
function is full.
@@ -402,8 +396,6 @@ typedef void (*napi_async_complete_callback)(napi_env env,
402
396
403
397
#### napi_threadsafe_function_call_js
404
398
405
- > Stability: 2 - Stable
406
-
407
399
Function pointer used with asynchronous thread-safe function calls. The callback
408
400
will be called on the main thread. Its purpose is to use a data item arriving
409
401
via the queue from one of the secondary threads to construct the parameters
@@ -4600,8 +4592,6 @@ prevent the event loop from exiting. The APIs `napi_ref_threadsafe_function` and
4600
4592
4601
4593
### napi_create_threadsafe_function
4602
4594
4603
- > Stability: 2 - Stable
4604
-
4605
4595
<!-- YAML
4606
4596
added: v10.6.0
4607
4597
napiVersion: 4
@@ -4644,8 +4634,6 @@ parameters and with `undefined` as its `this` value.
4644
4634
4645
4635
### napi_get_threadsafe_function_context
4646
4636
4647
- > Stability: 2 - Stable
4648
-
4649
4637
<!-- YAML
4650
4638
added: v10.6.0
4651
4639
napiVersion: 4
@@ -4663,8 +4651,6 @@ This API may be called from any thread which makes use of `func`.
4663
4651
4664
4652
### napi_call_threadsafe_function
4665
4653
4666
- > Stability: 2 - Stable
4667
-
4668
4654
<!-- YAML
4669
4655
added: v10.6.0
4670
4656
napiVersion: 4
@@ -4692,8 +4678,6 @@ This API may be called from any thread which makes use of `func`.
4692
4678
4693
4679
### napi_acquire_threadsafe_function
4694
4680
4695
- > Stability: 2 - Stable
4696
-
4697
4681
<!-- YAML
4698
4682
added: v10.6.0
4699
4683
napiVersion: 4
@@ -4715,8 +4699,6 @@ This API may be called from any thread which will start making use of `func`.
4715
4699
4716
4700
### napi_release_threadsafe_function
4717
4701
4718
- > Stability: 2 - Stable
4719
-
4720
4702
<!-- YAML
4721
4703
added: v10.6.0
4722
4704
napiVersion: 4
@@ -4744,8 +4726,6 @@ This API may be called from any thread which will stop making use of `func`.
4744
4726
4745
4727
### napi_ref_threadsafe_function
4746
4728
4747
- > Stability: 2 - Stable
4748
-
4749
4729
<!-- YAML
4750
4730
added: v10.6.0
4751
4731
napiVersion: 4
@@ -4766,8 +4746,6 @@ This API may only be called from the main thread.
4766
4746
4767
4747
### napi_unref_threadsafe_function
4768
4748
4769
- > Stability: 2 - Stable
4770
-
4771
4749
<!-- YAML
4772
4750
added: v10.6.0
4773
4751
napiVersion: 4
0 commit comments