Operator overloading revisited
brendan at mozilla.com
Wed Jul 22 11:14:12 PDT 2009
On Jul 22, 2009, at 3:10 AM, Christian Plesner Hansen wrote:
>> The current class proposal,
>> has zero inheritance.
> I was under the impression that the plan was to develop some form of
> inheritance model too. The strawman says that there is no inheritance
> to keep the design simple. Are you sure you're not throwing the baby
> out with the bathwater here?
Nothing is thrown out by starting simple and then considering our
We all know many ways (too many!) to support inheritance. Would it
help to pick a winner prematurely, compared to giving people sugar for
high-integrity factories, which they must write the long way in ES5,
or not at all in current JS?
More information about the es-discuss