Hacker GitHub

← All repos

tc39/proposal-private-fields

View on GitHub ↗ ★ 316 HTML archived

A Private Fields Proposal for ECMAScript

9 mentions on Hacker News by 9 people: 1 story, 8 comments · first 2017-08-03 · latest 2023-05-11

Mentions per year 9 mentions · busiest year 2017 (3)
20082026
  1. …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 .
  2. …which has allowed `_` at the start of an identifier or (public) property name for a long time. -- https://github.com/tc39/proposal-private-fields/blob/master/...
    comment by Madeindjs · 2021-06-13 · in Implementing Private Fields for JavaScript
  3. This is all covered here: https://github.com/tc39/proposal-private-fields/blob/master/...
    comment by elondaits · 2021-06-13 · in Implementing Private Fields for JavaScript
  4. Here’s what they said in the proposal https://github.com/tc39/proposal-private-fields/blob/master/...
    comment by fossilwater · 2021-06-13 · in Implementing Private Fields for JavaScript
  5. …inheritance with syntax sugar. In this future the `#` will be just a huge annoyance. #33 : https://github.com/tc39/proposal-private-fields/issues/33 2 : https://github.com/tc39/proposal-class-fields/blob/master/PR... 3 :…
    comment by drinchev · 2018-12-18 · in V8 release v7.2
  6. [1] While others have corrected you, just to be clear, this is something they addressed in the FAQ. https://github.com/tc39/proposal-private-fields/blob/master/... [2] This is addressed here: https://github.com/tc39/proposal-private-fields/…
  7. I think the concern is that if you look here: https://github.com/tc39/proposal-private-fields/issues/14 and other places, you'll see this massive push back from the community, yet the proposal is moving forward regardless.
  8. Background for this proposal and discussion can be found in this repo’s README and additional docs: https://github.com/tc39/proposal-private-fields