W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2015

[Bug 29004] FrozenArray only provides shallow immutability

From: <nobody@w3.org>
Date: Fri, 31 Jul 2015 18:05:56 +0000
To: public-script-coord@w3.org
Message-ID: <bug-29004-3890-kJSa9Ns86w@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29004

Travis Leithead [MSFT] <travil@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |travil@microsoft.com

--- Comment #2 from Travis Leithead [MSFT] <travil@microsoft.com> ---
I want to be cautious here--I agree with what hixie has said in the past, that
supplying frozen objects from the platform is an anti-pattern that seems
contrary to the platform's "configurable" nature by default. This comment was
made on the initial definition of FrozenArray<T> and now you are proposing
making this a *deep* operation.

Since we don't generally do this for dictionaries (make them frozen), I'm
wondering why we have this need for deep frozen arrays?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 31 July 2015 18:06:04 UTC

This archive was generated by hypermail 2.3.1 : Friday, 31 July 2015 18:06:05 UTC