doc: mark N-API thread-safe function stable
The various TSFN APIs are marked as stable, but the TSFN heading itself is still marked as experimental. PR-URL: https://github.com/nodejs/node/pull/28643 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
This commit is contained in:
parent
febdf39fdf
commit
efc39464b0
@ -4542,8 +4542,6 @@ NAPI_EXTERN napi_status napi_get_uv_event_loop(napi_env env,
|
|||||||
<!--lint disable no-unused-definitions remark-lint-->
|
<!--lint disable no-unused-definitions remark-lint-->
|
||||||
## Asynchronous Thread-safe Function Calls
|
## Asynchronous Thread-safe Function Calls
|
||||||
|
|
||||||
> Stability: 1 - Experimental
|
|
||||||
|
|
||||||
JavaScript functions can normally only be called from a native addon's main
|
JavaScript functions can normally only be called from a native addon's main
|
||||||
thread. If an addon creates additional threads, then N-API functions that
|
thread. If an addon creates additional threads, then N-API functions that
|
||||||
require a `napi_env`, `napi_value`, or `napi_ref` must not be called from those
|
require a `napi_env`, `napi_value`, or `napi_ref` must not be called from those
|
||||||
|
Loading…
x
Reference in New Issue
Block a user