tc39/proposal-class-fields issues and pull requests

#100 - A summary of feedback regarding the # sigil prefix

Issue - State: closed - Opened by glen-84 over 6 years ago - 391 comments

#100 - A summary of feedback regarding the # sigil prefix

Issue - State: closed - Opened by glen-84 over 6 years ago - 391 comments

#99 - The '#' looks awful, please change it

Issue - State: closed - Opened by gynet over 6 years ago - 3 comments

#99 - The '#' looks awful, please change it

Issue - State: closed - Opened by gynet over 6 years ago - 3 comments

#98 - Normative: Thread through lexically scoped private names

Pull Request - State: closed - Opened by littledan over 6 years ago

#98 - Normative: Thread through lexically scoped private names

Pull Request - State: closed - Opened by littledan over 6 years ago

#97 - Editorial: Fix up creating the internal slots for private names

Pull Request - State: closed - Opened by littledan over 6 years ago

#97 - Editorial: Fix up creating the internal slots for private names

Pull Request - State: closed - Opened by littledan over 6 years ago

#96 - Clarify that private fields can be accessed from within eval

Issue - State: open - Opened by littledan over 6 years ago - 6 comments
Labels: editorial

#96 - Clarify that private fields can be accessed from within eval

Issue - State: open - Opened by littledan over 6 years ago - 6 comments
Labels: editorial

#95 - Breaking encapsulation?

Issue - State: closed - Opened by jwalton over 6 years ago - 3 comments

#95 - Breaking encapsulation?

Issue - State: closed - Opened by jwalton over 6 years ago - 3 comments

#94 - Alternate strawman idea

Issue - State: closed - Opened by dead-claudia over 6 years ago - 8 comments

#94 - Alternate strawman idea

Issue - State: closed - Opened by dead-claudia over 6 years ago - 8 comments

#93 - use-case for private-fields? as a developer working on a web-project, can you give examples where private-fields would be useful?

Issue - State: closed - Opened by kaizhu256 over 6 years ago - 9 comments

#93 - use-case for private-fields? as a developer working on a web-project, can you give examples where private-fields would be useful?

Issue - State: closed - Opened by kaizhu256 over 6 years ago - 9 comments

#92 - Normative: End `this` TDZ before running initializers

Pull Request - State: closed - Opened by littledan over 6 years ago - 6 comments

#92 - Normative: End `this` TDZ before running initializers

Pull Request - State: closed - Opened by littledan over 6 years ago - 6 comments

#91 - FAQ tweaks

Pull Request - State: closed - Opened by bakkot over 6 years ago - 1 comment

#91 - FAQ tweaks

Pull Request - State: closed - Opened by bakkot over 6 years ago - 1 comment

#90 - private and protected are like static and super

Issue - State: closed - Opened by d8corp over 6 years ago - 26 comments

#90 - private and protected are like static and super

Issue - State: closed - Opened by d8corp over 6 years ago - 26 comments

#89 - Сlass field location

Issue - State: closed - Opened by d8corp over 6 years ago - 17 comments

#89 - Сlass field location

Issue - State: closed - Opened by d8corp over 6 years ago - 17 comments

#88 - Allow let bindings in class declaration

Issue - State: closed - Opened by oskardahlberg over 6 years ago - 3 comments

#88 - Allow let bindings in class declaration

Issue - State: closed - Opened by oskardahlberg over 6 years ago - 3 comments

#87 - Consistency across all uses of properties, just like with regular properties.

Issue - State: closed - Opened by trusktr over 6 years ago - 5 comments

#87 - Consistency across all uses of properties, just like with regular properties.

Issue - State: closed - Opened by trusktr over 6 years ago - 5 comments

#86 - What about protected fields?

Issue - State: closed - Opened by trusktr over 6 years ago - 5 comments

#86 - What about protected fields?

Issue - State: closed - Opened by trusktr over 6 years ago - 5 comments

#85 - Problematic that classes are still unnamed in static initializers?

Issue - State: closed - Opened by anba over 6 years ago - 24 comments
Labels: semantics

#85 - Problematic that classes are still unnamed in static initializers?

Issue - State: closed - Opened by anba over 6 years ago - 24 comments
Labels: semantics

#84 - Is it too late to exchange @ / # usage?

Issue - State: closed - Opened by hax over 6 years ago - 34 comments

#84 - Is it too late to exchange @ / # usage?

Issue - State: closed - Opened by hax over 6 years ago - 34 comments

#83 - Allow to mark class fields as readonly

Issue - State: closed - Opened by bschaepper over 6 years ago - 48 comments

#83 - Allow to mark class fields as readonly

Issue - State: closed - Opened by bschaepper over 6 years ago - 48 comments

#82 - Discussion/Proposal using alternative new syntax with "Symbol.for(this)"

Issue - State: closed - Opened by eddyw over 6 years ago - 9 comments

#82 - Discussion/Proposal using alternative new syntax with "Symbol.for(this)"

Issue - State: closed - Opened by eddyw over 6 years ago - 9 comments

#81 - Consider re-separating Class proposals

Issue - State: closed - Opened by justsml over 6 years ago - 21 comments

#81 - Consider re-separating Class proposals

Issue - State: closed - Opened by justsml over 6 years ago - 21 comments

#80 - Why not use arrow functions to bind member functions in proposal example?

Issue - State: closed - Opened by arthur-tacca over 6 years ago - 29 comments

#80 - Why not use arrow functions to bind member functions in proposal example?

Issue - State: closed - Opened by arthur-tacca over 6 years ago - 29 comments

#79 - Preserve all current syntax, but add support for dynamicity

Issue - State: closed - Opened by EthanRutherford over 6 years ago - 10 comments

#79 - Preserve all current syntax, but add support for dynamicity

Issue - State: closed - Opened by EthanRutherford over 6 years ago - 10 comments

#78 - Reword note implying shorthand syntax

Pull Request - State: closed - Opened by bakkot over 6 years ago

#78 - Reword note implying shorthand syntax

Pull Request - State: closed - Opened by bakkot over 6 years ago

#77 - Please do not use "#"

Issue - State: closed - Opened by babakness over 6 years ago - 97 comments

#77 - Please do not use "#"

Issue - State: closed - Opened by babakness over 6 years ago - 97 comments

#76 - Class-Block scope declaration

Issue - State: closed - Opened by shannon over 6 years ago - 4 comments

#76 - Class-Block scope declaration

Issue - State: closed - Opened by shannon over 6 years ago - 4 comments

#75 - Make # an object on the instance

Issue - State: closed - Opened by shannon over 6 years ago - 77 comments

#75 - Make # an object on the instance

Issue - State: closed - Opened by shannon over 6 years ago - 77 comments

#74 - Array syntax for private properties

Issue - State: closed - Opened by shdwjk over 6 years ago - 12 comments

#74 - Array syntax for private properties

Issue - State: closed - Opened by shdwjk over 6 years ago - 12 comments

#73 - Remove the private fields idea ("#"), at least for now

Issue - State: closed - Opened by TheNavigateur over 6 years ago - 16 comments

#72 - Preventing name collisions between public and private properties

Issue - State: closed - Opened by mbrowne over 6 years ago - 12 comments

#72 - Preventing name collisions between public and private properties

Issue - State: closed - Opened by mbrowne over 6 years ago - 12 comments

#71 - Question regarding nested classes

Issue - State: closed - Opened by billinghamj over 6 years ago - 1 comment

#71 - Question regarding nested classes

Issue - State: closed - Opened by billinghamj over 6 years ago - 1 comment

#70 - Class field definitions are not limited to Identifiers

Issue - State: closed - Opened by gibson042 over 6 years ago - 2 comments

#69 - Proposal to avoid the sigil

Issue - State: closed - Opened by dead-claudia over 6 years ago - 9 comments

#69 - Proposal to avoid the sigil

Issue - State: closed - Opened by dead-claudia over 6 years ago - 9 comments

#68 - Fix ASI error in readme

Pull Request - State: closed - Opened by bakkot over 6 years ago

#68 - Fix ASI error in readme

Pull Request - State: closed - Opened by bakkot over 6 years ago

#67 - Editorial: Describe ASI hazards

Pull Request - State: closed - Opened by littledan almost 7 years ago - 1 comment

#67 - Editorial: Describe ASI hazards

Pull Request - State: closed - Opened by littledan almost 7 years ago - 1 comment

#66 - Document initialization order and other semantic details at a high level

Issue - State: closed - Opened by littledan almost 7 years ago - 1 comment

#66 - Document initialization order and other semantic details at a high level

Issue - State: closed - Opened by littledan almost 7 years ago - 1 comment

#65 - Normative: Remove static fields

Pull Request - State: closed - Opened by littledan almost 7 years ago - 1 comment

#64 - Add private field syntax readme

Pull Request - State: closed - Opened by bakkot almost 7 years ago - 1 comment

#64 - Add private field syntax readme

Pull Request - State: closed - Opened by bakkot almost 7 years ago - 1 comment

#63 - Proposal: `#` shorthand for private _and_ public fields

Issue - State: closed - Opened by rattrayalex almost 7 years ago - 15 comments

#63 - Proposal: `#` shorthand for private _and_ public fields

Issue - State: closed - Opened by rattrayalex almost 7 years ago - 15 comments

#62 - Context of "this" in properties definition

Issue - State: closed - Opened by syabro almost 7 years ago - 11 comments

#62 - Context of "this" in properties definition

Issue - State: closed - Opened by syabro almost 7 years ago - 11 comments

#61 - Use both the # sigil and keywords

Issue - State: closed - Opened by lpd-au almost 7 years ago - 17 comments

#61 - Use both the # sigil and keywords

Issue - State: closed - Opened by lpd-au almost 7 years ago - 17 comments

#60 - Should private fields be per class execution, or based on source position?

Issue - State: closed - Opened by littledan almost 7 years ago - 40 comments

#60 - Should private fields be per class execution, or based on source position?

Issue - State: closed - Opened by littledan almost 7 years ago - 40 comments

#59 - What about protected methods, better declaration of private fields, private async functions, and destructuring?

Issue - State: closed - Opened by eddyw almost 7 years ago - 35 comments

#59 - What about protected methods, better declaration of private fields, private async functions, and destructuring?

Issue - State: closed - Opened by eddyw almost 7 years ago - 35 comments

#58 - this.onclick = this.clicked.bind(this);

Issue - State: closed - Opened by dmitriid almost 7 years ago - 17 comments

#58 - this.onclick = this.clicked.bind(this);

Issue - State: closed - Opened by dmitriid almost 7 years ago - 17 comments

#57 - Tooling implementation status

Issue - State: open - Opened by vjpr almost 7 years ago - 12 comments

#57 - Tooling implementation status

Issue - State: open - Opened by vjpr almost 7 years ago - 12 comments

#56 - Proposal: keyword to replace `#` sigil

Issue - State: closed - Opened by rattrayalex almost 7 years ago - 82 comments

#56 - Proposal: keyword to replace `#` sigil

Issue - State: closed - Opened by rattrayalex almost 7 years ago - 82 comments

#55 - DefineFields: how to tests observable abrupt completion for field with IsAnonymouseFunctionDefinition=true

Issue - State: closed - Opened by spectranaut almost 7 years ago - 2 comments

#55 - DefineFields: how to tests observable abrupt completion for field with IsAnonymouseFunctionDefinition=true

Issue - State: closed - Opened by spectranaut almost 7 years ago - 2 comments

#54 - Normative: Ban static private field declarations

Pull Request - State: closed - Opened by littledan almost 7 years ago - 1 comment

#54 - Normative: Ban static private field declarations

Pull Request - State: closed - Opened by littledan almost 7 years ago - 1 comment

#53 - Typo in ClassElementEvaluation

Issue - State: closed - Opened by spectranaut almost 7 years ago

#53 - Typo in ClassElementEvaluation

Issue - State: closed - Opened by spectranaut almost 7 years ago

#52 - Expected behaviour question

Issue - State: closed - Opened by andyjansson almost 7 years ago - 1 comment

#52 - Expected behaviour question

Issue - State: closed - Opened by andyjansson almost 7 years ago - 1 comment

#51 - Adoption timeframe for major browsers?

Issue - State: closed - Opened by kirkouimet almost 7 years ago - 1 comment

#51 - Adoption timeframe for major browsers?

Issue - State: closed - Opened by kirkouimet almost 7 years ago - 1 comment

#50 - Typo in DefineFields

Issue - State: closed - Opened by spectranaut almost 7 years ago

#50 - Typo in DefineFields

Issue - State: closed - Opened by spectranaut almost 7 years ago

#49 - NonConstructorElementDefinitions should not exclude class fields

Issue - State: closed - Opened by littledan almost 7 years ago

GitHub / tc39/proposal-class-fields issues and pull requests