Uh oh!
There was an error while loading. Please reload this page.
tsfn: support direct calls to underlying napi_tsfn - #580
Conversation
KevinEady
commented
Oct 29, 2019
The implementation for this is based off previous napi meeting discussion, see #556 (comment) |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
mhdawson
commented
Oct 31, 2019
Looks reasonable to me @gabrielschulhof can you take a look at as well? |
| napi_status Napi::ThreadSafeFunction::NonBlockingCall(void* data) const | ||
| ``` | ||
| - `data`: Data to pass to `call_js_cb` specified when creating the tsfn via |
There was a problem hiding this comment.
| -`data`: Data to pass to `call_js_cb` specified when creating the tsfn via | |
| -`data`: Data to pass to `call_js_cb` specified when creating the thread-safe function via |
There was a problem hiding this comment.
After a nasty fight between 500s from GitHub's commit suggestion API and various force pushes, this is comment has been updated 👍
KevinEady
commented
Nov 5, 2019
Hi @mhdawson / @gabrielschulhof dunno what to do for this build failure: https://travis-ci.com/nodejs/node-addon-api/jobs/253158482 |
gabrielschulhof
commented
Nov 5, 2019
@KevinEady I restarted the job. |
KevinEady
commented
Nov 7, 2019
Hi @mhdawson just a reminder on landing this |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
mhdawson
commented
Nov 10, 2019
Landed as |
Fixes: #556