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:21:57 +0000
To: public-script-coord@w3.org
Message-ID: <bug-29004-3890-vQdPnKqG3n@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29004

--- Comment #4 from Travis Leithead [MSFT] <travil@microsoft.com> ---
(In reply to Boris Zbarsky from comment #3)
> The frozen thing is for when you want to keep returning the same object each
> time but don't want the caller to be able to modify it.

I think this is where my question is. There's nothing that prevents the
platform from keeping a reference to a non-frozen JS array and returning the
same instance over and over. Is there another requirement that I'm missing?
Such as, are platforms expecting to be able to grow/shrink/change the values in
the array instance themselves, while not allowing author code this privilege?

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

This archive was generated by hypermail 2.3.1 : Friday, 31 July 2015 18:21:59 UTC