Using __proto__ in object literals is not deprecated

[bakkot]

The __proto__ syntax (as opposed to the getter/setter) was moved out of Annex B in tc39/ecma262#2125. It's fine to use, and in fact is generally preferable to Object.create() (because it makes it easier to set up other normal data properties, and because it's syntax rather than an API call).

[CLAassistant]

All committers have signed the CLA.

[smith558]

@bakkot Is this not the consensus of the discussion you are referring to?

[bakkot]

@smith558 as that screenshot says, the use of the __proto__ syntax is not discouraged. It's only the use of the __proto__ accessor which is problematic.

[smith558]

@smith558 as that screenshot says, the use of the __proto__ syntax is not discouraged. It's only the use of the __proto__ accessor which is problematic.

Yeah, Could you explain to me what they mean by "proto syntax"? I understand the other 2 points but for me, those would be included under "proto syntax".

[bakkot]

{ __proto__: null } is special syntax (search for "isProtoSetter" in that section); it's a different thing than { foo: null }. That specific syntax is given meaning by the spec.

By contrast, obj.__proto__ is a normal property access, just like obj.foo. But there happens to be a getter/setter named __proto__ on Object.prototype, so if obj inherits from Object.prototype then this triggers the behavior of that getter/setter (just like how every other getter/setter works).

[smith558]

Change to obj.__proto__? Clashes with above paragraph when it's referenced as obj.__proto__ rather.

[smith558]

{ __proto__: null } is special syntax (search for "isProtoSetter" in that section); it's a different thing than { foo: null }. That specific syntax is given meaning by the spec.

By contrast, obj.__proto__ is a normal property access, just like obj.foo. But there happens to be a getter/setter named __proto__ on Object.prototype, so if obj inherits from Object.prototype then this triggers the behavior of that getter/setter (just like how every other getter/setter works).

I see. Thanks! I feel like Objects and Prototypes are very important concepts and a first-time reader may feel confused by seeing suggestions to "use" __proto__ and "not use" __proto__ (tho not in the same way) at once and the article changes proposed as it at this time do not fully convey the meaning and the differences in such way so as not to confuse the reader or teach them to use it correctly. (feedback)

[iliakan]

You mean that using __proto__ in {...} is ok, but get/set .__proto__ is not, right?

[iliakan]

@bakkot