|
|
|
|
|
|
by stasm
1197 days ago
|
|
|
> - # private... not sure why they didn't just use the "private" keyword, but I don't care. I almost always use TypeScript anyways One of the reasons was to allow private and public fields of the same name, so that subclasses are free to add own public fields without accidentally discovering private fields of superclasses. There were many more considerations that went into the design: https://github.com/tc39/proposal-class-fields/blob/main/PRIV.... There was a heated debate about this and the choice of the # sigil back in 2015 at the time private fields were being designed: https://github.com/tc39/proposal-private-fields/issues/14. |
|
|