On 2015/04/17 at 14:07:38, info wrote:
This completely will completely break io.js and node.js and a great many
add-ons.
Saying embedders should use ArrayBuffer is easy but there is a whole
ecosystem
built around the external array API and this change will have a
disproportional
impact on that; the churn is going to be enormous. I don't think this CL
should
land.
the only way going forward we could support this API is by completely
duplicating the current code, as the array buffer code is changing in a way
incompatible with this API.
otoh, I don't think it's going to be so much more worse than all the
changes to
our handle API...
... anyway. I'll bring this up for discussion, but don't get your hopes up
just
yet
https://codereview.chromium.org/1092923002/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
