Allen Wirfs-Brock wrote:
On May 30, 2012, at 4:15 PM, Brendan Eich wrote:

At last week's meeting we deferred super outside of class methods.

We talked about it, but I don't see the above statement captured in the minutes.

From Rick's notes of day 2:


AWB:
- Asserts that super is defined correctly for classes
(explanation)

Should super be allowed in all function forms or restricted to classes?

Resolution: Defer super outside of classes


See https://mail.mozilla.org/pipermail/es-discuss/2012-May/022838.html

   It also isn't clear what  you mean by "deferred".

One precedent:

http://wiki.ecmascript.org/doku.php?id=strawman:deferred

We sometimes kill things outright too.

What we agreed to last week: no |super| outside of classes in ES6, no Object.defineMethod in ES6. That's what I recall and what the notes say (re: |super|).

  In a previous message you said that @privateName was deferred which I 
interpret as meaning deferred until another meeting.
Missed ES6 but we have to consider misses that are errors to correct, yes. Sorry for using deferred two different ways -- |super| outside of classes was not in this category.

   We certainly need to talk about a way to define private keyed methods in 
class declarations and @name seems like the most likely alternative.  Similar, 
I think it is reasonable to say we deferred making a decision to have super 
outside of classes.

No, not from what I saw and what Rick recorded in the notes he took.

  That doesn't mean that there still isn't interest in doing so and that some 
of us want to consider talking about how to do so.

Sure,

Also, last week there was support for .( expressed both from the perspective of 
the Smalltalk-like cascaded expression use cases and from the definitional 
object extension perspective.

Those are two different use-cases, operational semantics, and (therefore) syntaxes, though -- this thread makes that pretty clear.

   My perception is that different people were had primary interests in the 
different use cases.  Just because we may be on the path of a solution to the  
cascaded expression use cases doesn't mean there isn't still interest and 
support for the definitional use cases.

Who said there isn't "interest"? We're trying to keep what's in ES6 consistent, which is why I used "deferred". I'd be happy deferring beyond strawman at this point. We need to button down ES6.

People can pursue many interests and we do Harmony work beyond ES6 even in the meetings, but the decision last week was not to put |super| outside of classes into ES6, and therefore not to put Object.defineMethod into ES6. I recall this clearly and Rick's notes have at least the first bit.

/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to