[v8-users] Re: [blink-dev] Intent to Ship: Public class fields

2018-10-17 Thread Adam Klein
LGTM. I'm super-excited about this shipping! On Wed, Oct 17, 2018 at 9:47 AM Sathya Gunasekaran wrote: > Contact Emails: > gsat...@chromium.org > > Spec: > https://github.com/tc39/proposal-class-fields > https://tc39.github.io/proposal-static-class-features/ > > The linked proposal includes priv

[v8-users] Re: [blink-dev] Intent to Ship: Public class fields

2018-10-17 Thread Sathya Gunasekaran
On Wed, Oct 17, 2018 at 10:51 AM PhistucK wrote: > > Are the specification and implementation compatible with the Babel based > implementation/interpretation of the feature? After all, previously > transpiled code could now be interpreted natively... > Unfortunately, this is also considered "Web

[v8-users] Re: [blink-dev] Intent to Ship: Public class fields

2018-10-17 Thread PhistucK
Are the specification and implementation compatible with the Babel based implementation/interpretation of the feature? After all, previously transpiled code could now be interpreted natively... Unfortunately, this is also considered "Web compatibility". ☆*PhistucK* On Wed, Oct 17, 2018 at 10:47

[v8-users] Re: [blink-dev] Intent to Ship: Public class fields

2018-10-17 Thread 'Mathias Bynens' via v8-users
LGTM On Wed, Oct 17, 2018 at 9:47 AM Sathya Gunasekaran wrote: > Contact Emails: > gsat...@chromium.org > > Spec: > https://github.com/tc39/proposal-class-fields > https://tc39.github.io/proposal-static-class-features/ > > The linked proposal includes private fields, but this intent to ship > is

[v8-users] Intent to Ship: Public class fields

2018-10-17 Thread Sathya Gunasekaran
Contact Emails: gsat...@chromium.org Spec: https://github.com/tc39/proposal-class-fields https://tc39.github.io/proposal-static-class-features/ The linked proposal includes private fields, but this intent to ship is only for public instance and static fields, not private fields. Summary: Public