Allen Wirfs-Brock (2014-03-26T18:48:43.000Z)
domenic at domenicdenicola.com (2014-04-11T22:42:42.982Z)
On Mar 26, 2014, at 11:24 AM, Jason Orendorff wrote: > Compatibility: Changing from throwing to not-throwing is usually ok. > In addition, I don't think Chrome implements this TypeError. So > presumably the web can't be depending on the exception. This change would not just eliminating a throw in strict mode. It is also change sloppy mode behavior where such assignments have been silently ignored since ES1. It would be a fundamental change to the meaning of the [[Writable]] property attribute. see http://wiki.ecmascript.org/doku.php?id=strawman:fixing_override_mistake (and links from that page) also see the recent discussion at https://github.com/getify/You-Dont-Know-JS/issues/91#issuecomment-38702332 So far we have not been able to reach a consensus on changing this. I don't know whether report actually adds any new information or whether it will help develop a consensus.