proposal-class-fields
proposal-class-fields copied to clipboard
Editorial: Mismatch in specificity between private fields and properties?
The spec text about how properties are represented is a bit high-level, with wording like "Let X be O's own property whose key is P." Private state, on the other hand, is an explicit List of Records, where one slot in the record is the private name, and the other is the value (this may change to a property descriptor, to take methods and decorators into account). I don't see a good reason why these should be different. Should one of them be more formal, or the other more informal?
cc @bterlson @allenwb @anba @erights @bakkot