| 03:00 | <Ashley Claymore> | Realising this wasn't about matching other private fields with the same, so the name of the field would all still be local and still minifiable. it's more that the lookup would have fewer guarantees. Because proxies, walking the proto chain could have side effects and give different answers. so couldn't assume AOT things like `#p in v === #p in v` |
| 10:02 | <Mathieu Hofman> | Yeah the fact that looking up a private field cannot trigger any user code is a nice property. Combined with the fact you wouldn't know which object the value came from is probably sufficient reason for this to have been the right choice. |