Hi,
David, I think I see where you are going: property descriptors are
basically bags of key/value properties, and maps are a more direct
representation of this concept than objects.
On the other hand, as so carefully explained by Allen, there currently
isn't really an issue with the mapping
Le 01/11/2012 10:37, Tom Van Cutsem a écrit :
On the other hand, as so carefully explained by Allen, there currently
isn't really an issue with the mapping between property descriptors
and objects: at all the boundary points, we make sure to properly
convert descriptors into well-behaved
Another argument against using maps is it can actually be pretty useful to
use the features that prototypal inheritance and the object model provides.
function Descriptor(configurable, enumerable){
this.configurable = configurable;
this.enumerable = enumerable;
}
Descriptor.prototype = {
Just wondering if this is actually meant/expected, I am talking about the
example here:
http://wiki.ecmascript.org/doku.php?id=harmony:observe#example
and the fact it should show something in console while in my opinion that
should show nothing since the Object.unobserve is called in the same
On Thu, Nov 1, 2012 at 4:32 PM, Andrea Giammarchi
andrea.giammar...@gmail.com wrote:
Just wondering if this is actually meant/expected, I am talking about the
example here:
http://wiki.ecmascript.org/doku.php?id=harmony:observe#example
I'm not sure I understand your point. The example is not
Bump.
I don't think Array.prototype.contains ever materialized on the proposals
page, and hasn't shown up in an ES6 draft.
Officially out for ES6, stuck in the queue, or dropped on the floor?
On Fri, Feb 24, 2012 at 4:40 PM, Rick Waldron waldron.r...@gmail.comwrote:
Allen, thank you for the
On Nov 1, 2012, at 6:03 AM, David Bruant wrote:
Le 31/10/2012 19:03, Allen Wirfs-Brock a écrit :
Let me summarize what I think is your concern.
In ES5, property descriptor records are a specification device that is used
to transport information about object properties between factored
Looking at the recent draft, I noticed that the WeakMap methods accept
primitive keys, converting them to objects, and acting like an object was
passed in. This differs from the current behavior of Chrome and Firefox, which
both throw if key is not an object. It seems, as the current draft
(Assuming that I understand the issue.)
The object to map refactoring matters whenever you don't know the keys in
advance. If you do, as is the case with property descriptors, objects are fine.
Then they are more like records than like maps.
Axel
[[[Sent from a mobile device. Please forgive
copy/paste bug!!
Allen
On Nov 1, 2012, at 9:05 AM, Nathan Wall wrote:
Looking at the recent draft, I noticed that the WeakMap methods accept
primitive keys, converting them to objects, and acting like an object was
passed in. This differs from the current behavior of Chrome and Firefox,
On file?
Nathan, thanks for catching this!
/be
Allen Wirfs-Brock wrote:
copy/paste bug!!
Allen
On Nov 1, 2012, at 9:05 AM, Nathan Wall wrote:
Looking at the recent draft, I noticed that the WeakMap methods
accept primitive keys, converting them to objects, and acting like an
object was
On Nov 1, 2012, at 10:40 PM, Brendan Eich wrote:
On file?
already fixed in my draft.
Nathan, thanks for catching this!
/be
Allen Wirfs-Brock wrote:
copy/paste bug!!
Allen
On Nov 1, 2012, at 9:05 AM, Nathan Wall wrote:
Looking at the recent draft, I noticed that the WeakMap
12 matches
Mail list logo
