Marcin K

I pushed some changes to avoid upgrading whole lock files. Hopefully, this would make my change smal enough.

I am getting prettier errors in other places. Should I fix these as a part of this PR?

Not really. Either docs are wrong or there is a bug. It does not matter for me as I implemented limited version of just for myself.

```js class MyClass{ prop = 2; } ``` is equivalent to: ```js class MyClass{} MyClass.prototype.prop = 2; ``` or: ```js class MyClass{ constructor(){ this.prop = 2; } } ``` Can...

Then this proposal is about having an another way of creating instance properties? ```js class MyClass{ prop = 2 // instance property constructor(){ this.prop = 2 //another instance property }...

> @chyzwar, it's only roughly equivalent; its name is evaluated at a different time, it may have slightly different semantics, and it is expected to be easier for engines to...

> The impression I got when implementing this feature in V8 is that having objects be created with a static shape requires fewer hidden-class transitions, which is a nontrivial benefit...

> I don't think I agree. In many cases it's clearer to initialize them in the class body, as is common in other languages. This is especially true because the...

> I am telling you, having worked on this in V8 and having talked to other engine authors about this specific issue, that we don't expect this to the case....

Because function declaration and function statement hoist on the same scope/context. ```js cons a = function() {} function a(){} ``` @normanzb showcase how this will get confused by new people...