| 00:13 | <ljharb> | does it have to be a data property? can it be a getter that throws instead? (I’m sure I’m missing some context here) |
| 01:35 | <rbuckton> | They must be fields for a number of reasons: Fixed layout, performance, use with Atomics, etc. |
| 01:37 | <rbuckton> | Also interop with WASM |
| 05:24 | <ljharb> | the descriptor could have a fake getter/setter even if the property is a data property under the hood, i suppose |
| 05:33 | <Mathieu Hofman> | that seems extremely exotic |
| 05:34 | <Mathieu Hofman> | what would these fake getter and setters even do when plucked and called explicitly ? Also that means the engine needs to allocate them |
| 05:35 | <Mathieu Hofman> | I'd much rather say that the own prop MOPs don't "work" and all have undefined value fields |
| 14:39 | <shu> | agreed, fake getters sounds terrible |