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
Since the constructor isn't supported in Node 4.x, the current implementation has the effect of calling new Buffer(foo.b.bytes), making the new buffer point to the entire underlying array buffer of foo, that will also contain data for other buffers, because of pooling.
The text was updated successfully, but these errors were encountered:
Before
hxFromBytes(foo)
would generatebut that changed with 19a1e2b (and 9b24a89) to
However, the history of the
new Buffer(arrayBuffer, offset, length)
NodeJS constructor isn't as linear as one would hope:Since the constructor isn't supported in Node 4.x, the current implementation has the effect of calling
new Buffer(foo.b.bytes)
, making the new buffer point to the entire underlying array buffer offoo
, that will also contain data for other buffers, because of pooling.The text was updated successfully, but these errors were encountered: