An additional keyword like this would require a function to have a hidden
reference back to the instance. However, especially for `class` methods,
but also for ES5-style inheritance, or even for `class Foo {}
Foo.prototype.bar = function () {}`, methods are *shared*. You might have a
billion instances, but only one function that uses your new keyword - how
would the engine know which instance you were referring to?On Sat, Mar 9, 2019 at 7:50 AM Bergi <[email protected]> wrote: > Hi John, > > > I believe that it would be a trivial task for > > current static code analyzers to restrict usage of "this" for anyone > > opting in to use this new keyword exclusively. > > Static tooling, like the TypeScript compiler, can detect problematic > method usage already today. Sure, having a dedicated syntax for this > will make static analysis simpler, but I don't deem that a worthy > addition to the language. > > > As you mentioned, arrow functions might have their own > > problems. Wouldn't such an alternative keyword be a good addition to our > > toolkit anyway? > > What I was trying to say is that your proposed alternative has exactly > the same problems as instance-member arrow functions have today. > > Best regards, > Bergi > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
