— Too many implementation details to overcome
And mechanisms relating to data sharing, callback invocation etc... there are even many ways to invoke JS from C++
— If i put properties on prototype but not in constructor, will it be cached later when i set those props?
Message permanent page
— Way I see it is... a C++ module can be like a system call viferga
— And interruptions stop while those run
— And well, why would you use a C++ module except to interact with hardware somehow
— That is not something HzScript even is supposed to interact with or be concerned with
— I think it would be faster lookup time
— After setting on instance
— If I read that correctly you mean set on prototype, then instantiate, then set on instance outside constructor?
— So like thing.prototype.thing becomes thing.thing