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
As a result, this metadata was not updated for node v4.0 and v4.1. Even if these releases are not considered LTS releases, I'm wondering if it's worth it to implement a workaround for this problem by hard-coding the type to int when V8's version is within the range of the versions used by node v4.0 and v4.1.
Hopefully nodejs/node#2959 will land soon and will be available in the next v4.x releases.
The text was updated successfully, but these errors were encountered:
nodejs/node#2959 which updates bit_field3's type and nodejs/node#2974 which adds ScopeInfo's constants to V8's post-mortem metadata have anded in nodejs/master, and are flagged to land in the next v4.x release.
So hopefully the post-mortem metadata for the next v4.x release of node will be more up to date.
https://codereview.chromium.org/1296743003/ landed in V8's master today and a PR to float it in node master and v4.x was sent today as well.
As a result, this metadata was not updated for node v4.0 and v4.1. Even if these releases are not considered LTS releases, I'm wondering if it's worth it to implement a workaround for this problem by hard-coding the type to
int
when V8's version is within the range of the versions used by node v4.0 and v4.1.Hopefully nodejs/node#2959 will land soon and will be available in the next v4.x releases.
The text was updated successfully, but these errors were encountered: