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 upImmutable Prototype Exotic Objects is underspecified #705
Comments
allenwb
added
the
editorial change
label
Oct 2, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
domenic
Oct 2, 2016
Member
+1. Nit: I'd replace "must not change" with "can not change" since otherwise the normative not-changing requirement is being duplicated in two places.
|
+1. Nit: I'd replace "must not change" with "can not change" since otherwise the normative not-changing requirement is being duplicated in two places. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
littledan
Oct 17, 2016
Member
Thanks for pointing this out; I'll prepare a spec match to make it match the other parts soon.
|
Thanks for pointing this out; I'll prepare a spec match to make it match the other parts soon. |
added a commit
to littledan/ecma262
that referenced
this issue
Nov 15, 2016
littledan
referenced this issue
Nov 15, 2016
Merged
Clean up definition of Immutable Prototype Exotic Objects #731
bterlson
closed this
in
#731
Nov 21, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
allenwb commentedOct 2, 2016
The specification for Immutable Prototype Exotic Objects is incomplete and does not fully follow the pattern used to specify other standard exotic objects. Other than for [[GetPrototypeOf]], an implementer would have to guess at the intended definition of the essential internal methods.
This can be corrected by replacing the single paragraph of 9.4.7 with something like the following :