Definitely TypeScript's system is better than the proposal. I often publicize private variables and privatize public variables (In other languages). The # scheme increases the effort to do so and increases the chances of bugs being introduced in doing so. This is why I oppose the # scheme.
I also don't accept the premises given in the justification, based on the very fact that changing the access status of a variable would make it clash with another variable, if this.x and this.#x were both allowed: I don't accept therefore that allowing this would be desirable let alone necessary. On Mon, 15 Jan 2018, 6:07 am Brandon Andrews, <[email protected]> wrote: > https://github.com/sirisian/ecmascript-class-member-modifiers > > Is this closer to what you think would be acceptable? Essentially > C++/TypeScript kind of modifiers. Or does that still have issues? > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
