Orthogonal-Classes
Orthogonal-Classes copied to clipboard
erights
Proposed EcmaScript Class Syntax clarifying orthogonal concerns
See https://github.com/tc39/proposal-class-public-fields/issues/61 See https://github.com/tc39/proposal-private-fields/issues/82
I'm curious why [this.#helper()](https://github.com/erights/Orthogonal-Classes/tree/9cf063e0bcdfa8a3bff2c07099dbd597fade1360#no-private-methods-on-prototypes) would be disallowed? This seems to be a very very common language pattern, but I've never understood a good reason for it. I understand that it's...
> Class scoped lexical function declarations If my mind is correctly understanding this I would just like to express that I think this is a wonderful idea. It also brought...
> In this design, if the "constructor" method definition is made static, then it is initialized to point at itself. What does this wording mean, that the constructor has a...
Private methods on the prototype are pretty useless as there is no convenient way to reference them. Consider: ```js class X { #helper() {}; //private method on prototye leader() {...
I like the aesthetics of having own methods to "complete the grid" and make an orthogonal system, but I'm wondering about the usage of this feature. I've heard from @sebmarkbage...
Should we have these? In particular, for a use case, some frameworks (cc @wycats @diervo) have mentioned a desire to have a way to observe changes in private fields. The...
Private constructors would have the referencing problems discussed more generally in https://github.com/erights/Orthogonal-Classes/issues/2 for prototype placement private methods. Also, if `#constructor() {}` just created a private #constructor field and suppresses the...
As you point out, in the "Open Questions" section, the application of a single visibility token to all elements of a BindingList is likely to be misunderstood. In particular, I...