W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2014

[Bug 23682] Fix the current [ArrayClass], [] and sequence<T> mess

From: <bugzilla@jessica.w3.org>
Date: Mon, 06 Oct 2014 22:49:58 +0000
To: public-script-coord@w3.org
Message-ID: <bug-23682-3890-tINIDCG3Uu@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23682

--- Comment #30 from Jonas Sicking <jonas@sicking.cc> ---
(In reply to Mark S. Miller from comment #21)
> As one example, the array of literal parts of
> a template string is deeply frozen, so that it can be safely shared among
> the multiple evaluations of the same template string expression.

Mark: can you confirm that Object.freeze() for an Array indeed makes the Array
immutable?

Object.freeze() in general doesn't make things immutable, however in the
special case of Arrays, it appears that it does. Could you confirm that that is
the case?

And that there's no risk that future changes to Array might introduce some way
of mutating frozen Arrays? Is the template string feature freezing Arrays in
order to make them immutable, or is it doing so in order to accomplish some
other goal?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 6 October 2014 22:50:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC