You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd wonder if a napi_is_detachable_arraybuffer would be more suitable and able to cover more situations. As internal buffers in V8 would not be detachable ( Also in JerryScript, which implements internal arraybuffer with inlined back store), an arraybuffer that has not been detached before would still be not detachable.
Activity
legendecas commentedon Oct 13, 2019
I'd wonder if a
napi_is_detachable_arraybufferwould be more suitable and able to cover more situations. As internal buffers in V8 would not be detachable ( Also in JerryScript, which implements internal arraybuffer with inlined back store), an arraybuffer that has not been detached before would still be not detachable.legendecas commentedon Oct 13, 2019
One might be concerning that
is_detachableis not defined in ECMA spec.mhdawson commentedon Oct 17, 2019
@legendecas agreed, we would like to stick to what is in the ECMA spec in most cases.
n-api: implement napi_is_detached_arraybuffer
n-api: implement napi_is_detached_arraybuffer
n-api: implement napi_is_detached_arraybuffer
n-api: implement napi_is_detached_arraybuffer
n-api: implement napi_is_detached_arraybuffer
n-api: implement napi_is_detached_arraybuffer
n-api: implement napi_is_detached_arraybuffer