Mark's reply is good. Another point: we incubate strawman proposals for 
indefinite future editions, we do not prematurely cut because something doesn't 
fit in ES6. So the strawmay count does not indicate language complexity in the 
next edition.

Also, bean-counting lots of little API wins of the kind crock has written up 
recently is not enlightening. Ideally library authors would do all that and any 
standardization would be de-jure recognition of de-facto standards (Array 
extras are the best example, Function bind and getters and setters _mutatis 
mutandis_).

The big ticket items IMHO remain modules, proxies, and scope wins (no global 
scope, let).

In light of the incubation argument and big-ticket items, I don't think value 
proxies break our complexity budget but they are very new. They're unlikely to 
get into ES6. Let's keep discussing here and working on the wiki as interest 
and time allow, and not try to kick them out for some false economy.

/be

On Jan 10, 2011, at 2:12 AM, Erik Corry wrote:

> 2011/1/10 thaddee yann tyl <[email protected]>:
>> I see no reason to name the "floordiv" trap that way. Python has a
> 
> Agreed.
> 
> On a slightly more high level note it seems like there is a very large
> number of complex proposals being poured into Harmony.  If they are
> all implemented the language will become unwieldy and complex both for
> users and implementers.  Is there a sense in which we have a
> 'complexity budget' or does the committee feel we can add all
> proposals to the language?
> 
> On the concrete proposal I note that the strawman claims this can be
> used to implement bignums, but it seems to me there is no way to
> implement storage of arbitrary size so that would appear to be
> impossible.  Am I missing something.
> 
> Another question:  As I read the proposal, the dispatch is on the left
> hand side of binary operators.  Does the proposal have a way for a+b
> to work where a is an old-fashioned number and b is a complex?
> 
> -- 
> Erik Corry
> _______________________________________________
> 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

Reply via email to