W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2010

Re: Adoption of the Typed Array Specification

From: Chris Marrin <cmarrin@apple.com>
Date: Fri, 14 May 2010 07:30:26 -0700
Cc: Oliver Hunt <oliver@apple.com>, arun@mozilla.com, es-discuss@mozilla.org, public-script-coord@w3.org, Erik Arvidsson <erik.arvidsson@gmail.com>
Message-id: <1F881D03-7A4B-49B3-9FC1-F5A177EA7735@apple.com>
To: Mike Shaver <mike.shaver@gmail.com>

On May 14, 2010, at 7:22 AM, Mike Shaver wrote:

> On Fri, May 14, 2010 at 2:09 AM, Oliver Hunt <oliver@apple.com> wrote:
>> The data is mutable, the length is not -- this is more in line with arrays in other languages, but more importantly the whole point of the typed array spec was to provide a compact typed storage mechanism.  Allowing the length to be changed runs counter to this as it effectively puts us back in the position of supporting sparse arrays.
> 
> I don't see why that's the case.  You can define the semantics such
> that length-extension zero-fills (or NaN-fills, if you like to hurt
> kittens) rather than permitting sparseness, and it would seem to meet
> all the requirements of the typedarray spec.

As Ollie mentioned, ArrayBuffers need to be able to be mapped to hardware storage (either on the CPU or GPU). So anything that might change the underlying storage address (such as resizing the array) would be problematic.
Received on Friday, 14 May 2010 14:31:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:02 UTC