{"action":"created","issue":{"url":"https://api.github.com/repos/tc39/ecma262/issues/1154","repository_url":"https://api.github.com/repos/tc39/ecma262","labels_url":"https://api.github.com/repos/tc39/ecma262/issues/1154/labels{/name}","comments_url":"https://api.github.com/repos/tc39/ecma262/issues/1154/comments","events_url":"https://api.github.com/repos/tc39/ecma262/issues/1154/events","html_url":"https://github.com/tc39/ecma262/issues/1154","id":308305590,"number":1154,"title":"Odd behavior with [[Set]] on non-frozen objects inheriting from frozen objects","user":{"login":"isiahmeadows","id":4483844,"avatar_url":"https://avatars1.githubusercontent.com/u/4483844?v=4","gravatar_id":"","url":"https://api.github.com/users/isiahmeadows","html_url":"https://github.com/isiahmeadows","followers_url":"https://api.github.com/users/isiahmeadows/followers","following_url":"https://api.github.com/users/isiahmeadows/following{/other_user}","gists_url":"https://api.github.com/users/isiahmeadows/gists{/gist_id}","starred_url":"https://api.github.com/users/isiahmeadows/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/isiahmeadows/subscriptions","organizations_url":"https://api.github.com/users/isiahmeadows/orgs","repos_url":"https://api.github.com/users/isiahmeadows/repos","events_url":"https://api.github.com/users/isiahmeadows/events{/privacy}","received_events_url":"https://api.github.com/users/isiahmeadows/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2018-03-24T22:48:08Z","updated_at":"2018-03-26T05:19:52Z","closed_at":null,"author_association":"NONE","body":"I can't tell if this is a spec bug or feature request. [But this came up just now on ES Discuss](https://esdiscuss.org/topic/something-like-object-freeze-but-not-inherited-from-prototypes), and it seems incredibly odd that [[Set]] doesn't seem to take into account some properties on non-frozen objects are inherited from frozen ones. Is there a reason it's checking the frozenness of the inherited object, when it's only the base object that such a property would be set if not frozen?\r\n\r\n```js\r\n// Adapted example\r\nconst proto = {foo: \"foo\", bar: \"bar\"}\r\nconst o = Object.create(proto)\r\n\r\no.foo = 1 // works\r\nObject.freeze(proto)\r\no.bar = 2 // fails?\r\n```"},"comment":{"url":"https://api.github.com/repos/tc39/ecma262/issues/comments/376049221","html_url":"https://github.com/tc39/ecma262/issues/1154#issuecomment-376049221","issue_url":"https://api.github.com/repos/tc39/ecma262/issues/1154","id":376049221,"user":{"login":"erights","id":273868,"avatar_url":"https://avatars3.githubusercontent.com/u/273868?v=4","gravatar_id":"","url":"https://api.github.com/users/erights","html_url":"https://github.com/erights","followers_url":"https://api.github.com/users/erights/followers","following_url":"https://api.github.com/users/erights/following{/other_user}","gists_url":"https://api.github.com/users/erights/gists{/gist_id}","starred_url":"https://api.github.com/users/erights/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/erights/subscriptions","organizations_url":"https://api.github.com/users/erights/orgs","repos_url":"https://api.github.com/users/erights/repos","events_url":"https://api.github.com/users/erights/events{/privacy}","received_events_url":"https://api.github.com/users/erights/received_events","type":"User","site_admin":false},"created_at":"2018-03-26T05:19:52Z","updated_at":"2018-03-26T05:19:52Z","author_association":"NONE","body":"I disagree with that reasoning too. I have ***never*** seen code in the wild that used inheritance that way on purpose. Does anyone know of a single example, aside from code to test or illustrate this very principle?\r\n\r\nThe agreement or not on this principle is an argument we still need to have. We should still fix the override mistake."}}
{"actor":{"display_login":"erights"}}