-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
meta: V8 6.0 / TF & I tracking issue #13729
Comments
I'm not sure what you mean, TurboFan + Ignition is already the default in V8 5.9 which is in master. Unless there are specific "issues" with 6.0? |
I saw some issues that concluded with "let's wait for V8 to get better", and thought It would be good to track them. Either old issues that could be reevaluated now, or recent issues that will need reevaluation after 6.0. |
Quoting the
|
I'm working with WebAssembly and V8 6.0 lands ShareArrayBuffers which I'd like to be able to use with node:
What is the current release plan for V8 6.0? |
Should go into a future Node 8 release (before Node 8 goes LTS in October). |
@winksaville Full discussion is in nodejs/CTC#99 |
@winksaville By the way, you can already test even V8 6.1 with Node.js canary: |
[EDITING NOTE: I am going through and editing everything in this issue that refers to |
@vsemozhetbyt, GREAT I'll give it a try! |
I'm closing this as a dupe as we have a handful of issues already tracking this Comms plan: nodejs/CTC#155 If you think this meta issue is still useful please feel free to reopen |
Turns out I used it way less then expected, so closed is right. (and anyway could still be used for tracking without causing confusion). |
A reference point for things that need reevaluation after the next big V8 bump.
[edit]
Or now that TF & I is on.
The text was updated successfully, but these errors were encountered: