Le 09/02/2013 00:39, Claude Pache a écrit :
Since BC is not an issue, let's pick the semantic that is most conform to the existing
Ecmascript object model, and let's not invent a weird: true property
descriptor just because we think that __proto__ deserves one.
The goal is to standardise the
I am trying to understand the discussion and resolution of
'The Array Subclassing Kind Issue'. The issue (though not its
solution) seemed simple enough
class V extends Array { ... }
m = (new V()).map(val = val);
console.log( m instanceof V ); // false :(
and I was expecting solutions
Rick Waldron wrote:
# January 29 2013 Meeting Notes
* @@create is a well known symbol that when used as a property of a
constructor provides the alloca1on method for that constructor.
* New definition of the ordinary [[Construct]] :
1. Let creator be [[Get]] of this constructors @@create
One of the problems with map is that the return type of the function
might be different. With some pseudo syntax for types
function f(x : T) : V { ... }
var a : Array.T = ...
var b = a.map(f);
b is actually of type Array.V and not of Array.T
This becomes an issue with typed arrays at least.
On
On Feb 9, 2013, at 2:16 AM, Claus Reinke wrote:
I am trying to understand the discussion and resolution of
'The Array Subclassing Kind Issue'. The issue (though not its
solution) seemed simple enough
class V extends Array { ... }
m = (new V()).map(val = val);
console.log( m
Allen Wirfs-Brock wrote:
On Feb 9, 2013, at 2:16 AM, Claus Reinke wrote:
I am trying to understand the discussion and resolution of 'The
Array Subclassing Kind Issue'. The issue (though not its
solution) seemed simple enough
class V extends Array { ... } m = (new V()).map(val = val);
On Feb 9, 2013, at 3:01 PM, Herby Vojčík wrote:
Allen Wirfs-Brock wrote:
ethods.
The choice we agreed to, at the meeting is
1) Array.prototype.map produces the same kind of array that it was
applied to, so:
for the above example m instance of V will be true.
Allen Wirfs-Brock wrote:
Note that the enumerable attribute really only affects for-in enumeration (and
Object.keys), neither of which enumerates symbols anyway. That, means that the
enumerable attribute really has has no current meaning for symbol keyed properties. That
means we could
I know `StopIteration` is pretty baked in by now. But, most of the arguments I
can recall for it are that it’s better than `hasNext` + `next`, wherein you
have to keep two methods in sync. I saw the Dart iterator API the other day and
it provided a third alternative I thought the list might
9 matches
Mail list logo
