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

Re: ArrayClass should imply @@isConcatSpreadable

From: Allen Wirfs-Brock <allen@wirfs-brock.com>
Date: Mon, 28 Oct 2013 18:04:06 -0700
Cc: Boris Zbarsky <bzbarsky@MIT.EDU>, "public-script-coord@w3.org" <public-script-coord@w3.org>, es-discuss <es-discuss@mozilla.org>
Message-Id: <D3E97E0E-8BF0-4690-8E7A-32A65FAA4322@wirfs-brock.com>
To: Domenic Denicola <domenic@domenicdenicola.com>

On Oct 28, 2013, at 5:52 PM, Domenic Denicola wrote:

> From: Allen Wirfs-Brock [mailto:allen@wirfs-brock.com]
> 
>> So what's so onerous about returning a fresh array from the getter each time it was called.
> 
> The fact that `api.property !== api.property`.
> 

You mean people want to do identity checks of the value of the property? Why?

Sorry, for pushing too much on this, but issues like when to produce fresh objets, when its safe to share mutable object, and when there are object identity expectations are pretty fundamental issues when designing object based APIs.  

Allen
Received on Tuesday, 29 October 2013 01:04:41 UTC

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