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

Re: Adoption of the Typed Array Specification

From: Mike Shaver <mike.shaver@gmail.com>
Date: Fri, 14 May 2010 10:22:40 -0400
Message-ID: <AANLkTimTFkZq9tltMF8LjU_Y7U14sKLZ1AfQBzk5uX6x@mail.gmail.com>
To: Oliver Hunt <oliver@apple.com>
Cc: Alex Russell <alex@dojotoolkit.org>, arun@mozilla.com, public-script-coord@w3.org, Erik Arvidsson <erik.arvidsson@gmail.com>, es-discuss@mozilla.org
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.

Received on Friday, 14 May 2010 14:23:13 UTC

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