| 18:17 | <rickbutton> | does anyone off top-of-head recall the historical reasons behind why the Array prototype methods always throw when attempting to assign a non-writable length property, regardless of strictness, unlike the runtime semantics of an AssignmentExpression? |
| 18:50 | <bakkot> | all built-in functions are supposed to be imagined to be implemented in strict mode code |
| 18:50 | <bakkot> | it would be more strange if their behavior differed depending on whether they were called from strict mode or not, so it has to be one or the other, and behaving as if they were strict seems like the obvious choice |