Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upShould remove unnecessary [[Extensible]] assignments #1201
Comments
bmeck
self-assigned this
May 22, 2018
bmeck
added
needs editorial changes
good first patch
labels
May 22, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
rkirsling
Jun 4, 2018
Member
@bmeck: I was looking for a good first patch to tackle, but noticed that you've also self-assigned here. Do you mind if I submit a PR for this?
|
@bmeck: I was looking for a |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
bmeck
Jun 4, 2018
Member
@rkirsling feel free to make the PR, I accidentally set myself to this wehn making it and then changed it to be good first patch XD.
|
@rkirsling feel free to make the PR, I accidentally set myself to this wehn making it and then changed it to be good first patch XD. |
bmeck
removed their assignment
Jun 4, 2018
rkirsling
referenced this issue
Jun 4, 2018
Merged
Editorial: Don't explicitly set [[Extensible]] to true #1212
ljharb
closed this
in
#1212
Jun 4, 2018
rkirsling
referenced this issue
Jun 6, 2018
Merged
Editorial: Built-ins needn't initialize [[Extensible]] to true #1215
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
bmeck commentedMay 22, 2018
Default behavior is for it to be
trueper https://tc39.github.io/ecma262/#sec-ecmascript-standard-built-in-objects , but lots of builtins specify it to be true. This can lead to some confusion and thinking thattrueis not the default.