- From: <bugzilla@jessica.w3.org>
- Date: Mon, 06 Oct 2014 22:58:46 +0000
- To: public-webcrypto@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26322 --- Comment #4 from Boris Zbarsky <bzbarsky@mit.edu> --- > 1) Is there a concept of Frozen objects (maps) as well as of Frozen arrays ? There's a concept of frozen objects. Frozen means that you can't add or remove properties or change the values of existing properties. It does NOT mean that accessors or methods cannot manipulate internal slots. So for example, given a frozen ES Date you could still setMonth() on it. Also, please don't conflate "objects" and "maps". An ES Map can be frozen, but since all mutation happens via methods operating on an internal slot that does nothing to prevent mutation of the Map. > 2) Is it important that the JS array / object is created when the attribute is first accessed, rather than when the thing implementing the interface that contains that attribute is created ? Is the difference between the two observable? If you rely on IDL to create the object for you, then it'll get created on access, because that's when IDL knows to do the dictionary-to-object or sequence-to-object conversion. But afaict that's black-box identical to creating it sometime earlier, as long as the state the dictionary is based on is immutable. > Another approach, I guess, would be to use the new maplike IDL, Yes. > is that if we use maplike there is no JS object for this thing I have no idea what you mean there. For which thing? > It seems there is no arraylike ? There's [ArrayClass], which is fairly similar because all the array methods are generic. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Monday, 6 October 2014 22:58:48 UTC