Gabriel Schulhof
Gabriel Schulhof
Compare with the Nan implementation. The use of the persistent reference may stem from there. If so, it may be a good time to diverge, especially since we document that...
In fact, none of the Nan examples store a persistent reference to the JS instance. We should remove it.
@AeromXundes inheritance is an [unaddressed problem](https://github.com/nodejs/node-addon-api/issues/229) in the V8 implementation of N-API. That is, V8 exposes the ability to properly inherit from a JavaScript class only in a V8-specific fashion...
May we please have https://github.com/nodejs/node/pull/37217 in the next v14.x release? It should make backporting subsequent commits a lot easier.
FWIW I've started working on an approach where I write a V8 shim which uses the node-addon-api wrapper and inline functions to transform code that would normally link to V8...
Well, I'm running into a serious snag with my shim. In order to keep from having to heap-allocate my definition of class `Local` differs from V8 in that the value...
The other way of looking at it is that `Signature` and `FunctionTemplate` need to be pointer types, but then you cannot easily define `Signature::New` and `FunctionTemplate::New`.
@kkoopa yes, thank you!
Another potentially fundamental problem: Since the whole `v8` namespace is essentially a bunch of inline definitions it works well when building in Release mode, however, when building in Debug mode,...
A potential solution on gcc is `-Wl,-Bsymbolic`, but I'm not sure I'll find an equivalent for all supported platforms.