"in" operator throwing on primitives rationale (was: eval on non-strings)

2014-04-09 Thread Qantas 94 Heavy
On Mar 4, 2012, at 3:24 PM, Brendan Eich wrote: > Allen Wirfs-Brock wrote: Both of these were added to the spec. in ES3. They are probably >> exactly the sort of thing I was warning against when I mentioned point >> in time or spec. writer introduced inconsistencies. > > Yup. > (I was off TC

Re: Initializer expression on for-in syntax subject

2014-04-09 Thread Brendan Eich
Huzzah! /be Mike Taylor wrote: On 3/25/14, 13:23, Mike Taylor wrote: On 3/14/14, 15:53, Brendan Eich wrote: I say we should evangelize this site. I've filed https://bugzilla.mozilla.org/show_bug.cgi?id=987889 to track this. For those not following the bug, a fix for this has been committe

Re: Rewinding iterators

2014-04-09 Thread Tab Atkins Jr.
On Wed, Apr 9, 2014 at 1:51 PM, Marcus Stade wrote: > I don't think I'm making my case very clear, my apologies. Hopefully, I'll > be able to clarify in this message. > > >> No enforcement is required by the specification. If you create an >> iterator that doesn't fully conform to the iterator in

Re: Rewinding iterators

2014-04-09 Thread Marcus Stade
I don't think I'm making my case very clear, my apologies. Hopefully, I'll be able to clarify in this message. No enforcement is required by the specification. If you create an iterator > that doesn't fully conform to the iterator interface specification and then > get surprising results, its you

Re: Initializer expression on for-in syntax subject

2014-04-09 Thread Mike Taylor
On 3/25/14, 13:23, Mike Taylor wrote: On 3/14/14, 15:53, Brendan Eich wrote: I say we should evangelize this site. I've filed https://bugzilla.mozilla.org/show_bug.cgi?id=987889 to track this. For those not following the bug, a fix for this has been committed to the battlefield.com codebase