Private Properties Syntax

[tc39]

Private Properties Syntax

[bakkot]

See the FAQ for private fields.

In short: of course we started out trying to make it work with the same syntax used in other languages. That turns out not to work.

[littledan]

At the next TC39 meeting, I'll raise this concern again. However, I'm not sure how much more ground there is to cover here--this has already been thoroughly discussed in the private fields issues.

[bakkot]

@dinoboff See the FAQ for private fields.

[dinoboff]

So private x would lead to bad assumption. Can't an other keyword be used instead?

[bakkot]

We discussed the possibility of an additional keyword for declarations at TC39. Ultimately, we were pretty firm that the declaration should include the #, so that declaration would mirror use and to encourage the mental model that the # is part of the field name. At that point, we felt an additional keyword would just be additional noise for not much benefit.

[monolithed]

In my opinion the sigil # looks like a syntactic noise and I'd to see something more compatible with TypeScript and other languages.

class Foo {
   private x = 1;

   public y () {
        return this->x;
   }
}


let foo = new Foo();

foo.y(); // 1

Why not to use the arrow -> instead of the dot .?

[dinoboff]

@littledan I understand why access to private fields needs a specific syntax, but that's not true for the declaration. Was the possibility of having a keyword like private x used to declare a private field and using #x only to access it discussed?

[ljharb]

@monolithed for your first question, please read the FAQ (this is also answered about 3 comments up)