On 11/17/2011 10:03 PM, Dominic Cooney wrote:
On Fri, Nov 18, 2011 at 9:40 AM, Waldemar Horwat walde...@google.com
mailto:walde...@google.com wrote:
Array destructuring and length:
let [a, b, c, d, ... r] = {2: 3} | [1, 2]
Obvious: a is 1; b is 2.
What are c, d, and r?
c
Array destructuring and length:
let [a, b, c, d, ... r] = {2: 3} | [1, 2]
Obvious: a is 1; b is 2.
What are c, d, and r?
c = 2.
d = undefined.
r = empty.
Fixed property destructuring doesn't rely on length.
Vararg r destructuring uses length.
The semantics of length will match that of slice.
On Thu, Nov 17, 2011 at 7:40 PM, Waldemar Horwat walde...@google.comwrote:
Array destructuring and length:
let [a, b, c, d, ... r] = {2: 3} | [1, 2]
Obvious: a is 1; b is 2.
What are c, d, and r?
c = 2.
d = undefined.
r = empty.
Fixed property destructuring doesn't rely on length.
On Nov 17, 2011, at 4:40 PM, Waldemar Horwat wrote:
Tom: Use a null target to indicate a permanently virtual object.
Brendan: Proxy.DonJuan
He refuses to commit.
/be
___
es-discuss mailing list
es-discuss@mozilla.org
On Nov 17, 2011, at 5:20 PM, Rick Waldron wrote:
On Thu, Nov 17, 2011 at 7:40 PM, Waldemar Horwat walde...@google.com wrote:
Array.from(a) is superfluous because it's expressed even simpler as
[... a]. DaveH withdrew it.
Perhaps Array.from() was either misunderstood or miscommunicated. I
On Fri, Nov 18, 2011 at 9:40 AM, Waldemar Horwat walde...@google.comwrote:
Array destructuring and length:
let [a, b, c, d, ... r] = {2: 3} | [1, 2]
Obvious: a is 1; b is 2.
What are c, d, and r?
c = 2.
Nit: This should be c = 3, because {2: 3} means ({2: x} | [1, 2])[2] is x,
right?
d
Here are my meeting notes for today.
Waldemar
WebIDL: Can abstract interfaces have static members? Don't see why
not -- they'd just be spec sugar for adding the same static member to
concrete classes that derive from those abstract interfaces. As
usual, it would be a spec error to have a
7 matches
Mail list logo