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
{{ message }}
This repository was archived by the owner on Mar 25, 2018. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 25, 2018. It is now read-only.
I already fixed the kJSApiObjectType and kJSObjectType values (see this commit) and now I wonder if anything else is needed.
Also, do we only care about the changes in v8.h ?
@nodejs/ctc we need to have further discussion about this because of async/await. @ofrobots raised this at the last meeting - V8 doesn't yet have hooks for proper Promise inspection with AsyncHooks et. al. but exposing async/await is going to drive much heavier adoption of native Promises. Is this a situation we are comfortable with in the short term while we wait for deeper hooks or do we want to postpone until we have the tools we need to provide proper runtime inspection?
FYI if you didn't realise already, 5.5 is the one that unflags async/await, it's really the only major JS feature.
I already fixed the kJSApiObjectType and kJSObjectType values (see this commit) and now I wonder if anything else is needed.
IndexedPropertyHandlerConfiguration and NamedPropertyHandlerConfiguration picked up extra fields.
EmbedderHeapTracer has new virtual methods. I would expect that to change the vtable of derived classes but abi-compliance-checker doesn't seem to think it's an issue.
You could try reverting it to the old API but in the specific case of EmbedderHeapTracer I'm not sure if it's worth the hassle. It's only useful to embedders (i.e., node.js, but we don't use it), it's not something add-ons would or should use. If a tree falls and no one is around to hear it...
Activity
matthewloring commentedon Nov 7, 2016
The ABI patch for 5.0/5.1 fixed all incompatibilities in the
includedirectory (v8-debug.h,v8-platform.h, etc).rvagg commentedon Nov 8, 2016
@nodejs/ctc we need to have further discussion about this because of async/await. @ofrobots raised this at the last meeting - V8 doesn't yet have hooks for proper Promise inspection with AsyncHooks et. al. but exposing async/await is going to drive much heavier adoption of native Promises. Is this a situation we are comfortable with in the short term while we wait for deeper hooks or do we want to postpone until we have the tools we need to provide proper runtime inspection?
FYI if you didn't realise already, 5.5 is the one that unflags async/await, it's really the only major JS feature.
bnoordhuis commentedon Nov 8, 2016
IndexedPropertyHandlerConfiguration and NamedPropertyHandlerConfiguration picked up extra fields.
EmbedderHeapTracer has new virtual methods. I would expect that to change the vtable of derived classes but abi-compliance-checker doesn't seem to think it's an issue.
targos commentedon Nov 10, 2016
What would be the way to handle it?
Re async/await: We could float a patch to keep it behind a flag until we decide it's ready for production.
bnoordhuis commentedon Nov 10, 2016
You could try reverting it to the old API but in the specific case of EmbedderHeapTracer I'm not sure if it's worth the hassle. It's only useful to embedders (i.e., node.js, but we don't use it), it's not something add-ons would or should use. If a tree falls and no one is around to hear it...
targos commentedon Nov 15, 2016
Thanks. I'll move the discussion to a PR where the changes can be more easily seen
Merged: [debug] Disable debug events if JS execution is disallowed
Version 5.4.500.42
Merged: Squashed multiple commits.
Version 5.4.500.43
Revert of [debugger] Migrate more debugger tests to inspector (patchset
Revert of [serializer] print use count of external references. (patch…
Version 5.6.326.1