V8 release v7.2
> V8 v7.2 adds support for public class [1] fields. Support for private class [2] fields is planned for a future V8 release.<p>For those who don't know private class fields add the weird "#" character for defining them inside the `class {}` block.<p><pre><code>    class IncreasingCounter {
       #count = 0;
       get value() {
           console.log('Getting the current value!');
           return this.#count;
       }
       increment() {
           this.#count++;
       }
    }
</code></pre>
This looks way worse than having what TypeScript did by introducing `public` / `private` keywords. Is there any body
which votes for es-next features such as this one? I wonder how the "#" private field popped up in Chrome specs.<p>1 : <a href="https://developers.google.com/web/updates/2018/12/class-fields" rel="nofollow">https://developers.google.com/web/updates/2018/12/class-fiel...</a><p>2 : <a href="https://developers.google.com/web/updates/2018/12/class-fields#private_class_fields" rel="nofollow">https://developers.google.com/web/updates/2018/12/class-fiel...</a>