- From: <bugzilla@jessica.w3.org>
- Date: Tue, 10 Jun 2014 01:50:36 +0000
- To: public-script-coord@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23369 --- Comment #15 from Boris Zbarsky <bzbarsky@mit.edu> --- > because it allows the script environment to manipulate the underlying bytes > while the Promise-d operation continues Which may be the right thing in some rare cases, in fact (e.g. if the Promise-d operation is not actually doing anything with those bytes). > or 'copy on write' (ruled out by implementors as complexity/performance > overhead for the common case of ArrayBuffers I'd think that except for performance characteristics "copy on write" is not black-box distinguishable from "copy", no? > I would expect that, since ArrayBufferViews are seen as valid inputs, a 'copy' > approach is desirable for consistency I don't think we should be forcing a copy on people, though we should probably have guidance that says that it's the appropriate thing to do if you plan to actually asynchronously use the data that was passed in. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Tuesday, 10 June 2014 01:50:38 UTC