The first issue (in chronological order) with that proposal is the lack of motivation. What is the problem that the proposal is trying to solve?
And since we are speaking of explosion of language complexity: It is good to try to solve the problem with existing syntax, in order to judge if the addition is worthwhile. But since we don't even know what the problem is, we can't even try. (I understand that my remarks are not what the original message asked for. But I think it is important to underline that there are fundamental question that must arise before "Is it implementable (in sweet.js or whatever)?") In the document it is said: "It also provides an elegant solution to the so-called existential operator problem." What is the problem and the solution? A concrete example would help. (Personally I’m particularly confused with that statement, because in situations where I want the existential operator, I certainly don’t want to invert the order of the key and the object.) —Claude > Le 20 juin 2015 à 06:30, Bob Myers <[email protected]> a écrit : > > In the spirit of the discussion about language complexity and extensibility, > consider the following brain-addled, pre-strawman proposal for a new pick > operator. > > http://rtm.github.io/boberator.html <http://rtm.github.io/boberator.html> > > I wonder if whatever macro-like facilities make their way into ES 20XX will > be able to handle this. I suspect this is beyond the capabilities of sweet, > but haven't really tried. > > Bob > > _______________________________________________ > 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
