Re: Mutability of CryptoOperationData

25 îêò. 2013 ã., â 22:51, Ryan Sleevi <sleevi@google.com> íàïèñàë(à):
> I dislike having to have side effects on the inputs, especially since sequence is defined to make a copy (as opposed to array).
> 
> This implies copy/copy-on-write already, per WebIDL, unless I'm incorrectly interpreting the sequence semantics.
> 

I think that the sequence itself is copied, but it’s not a deep copy. So no, the spec currently doesn’t resolve issues caused by mutability of ArrayBuffers.

Suggesting copy on write would be somewhat unprecedented I think. I don’t have a strong opinion about copy on write vs. freezing, but I imagine that TC39 folks may have such.

- WBR, Alexey Proskuryakov

Received on Saturday, 26 October 2013 06:05:31 UTC