Re: Syntax to get same object that method was called on (Easy methodchaining)

Hello, it's me, long-time lurker and person whose opinion shouldn't matter. I find the syntax and semantics of this to be nothing I've ever had a use case for, and I think it would make the language more complicated without much benefit. But if JS really wanted something like this, I'd prefer to

What does it mean to be web-compatible?

I got curious after reading the Array.prototype.contains thread. I understand it means 'old things on the Web will break', but is there some cutoff? Based on number sites or number of affected users? Couldn't find a definition searching esdiscuss.org - apologies if it's been discussed. Cheers!

Re: What does it mean to be web-compatible?

Thanks! 0.001% of what? On 08/10/2014 8:33 AM, Tab Atkins Jr. jackalm...@gmail.com wrote: On Tue, Oct 7, 2014 at 2:27 PM, Adam Ahmed aah...@atlassian.com wrote: I got curious after reading the Array.prototype.contains thread. I understand it means 'old things on the Web will break

Re: Proposal: Generator returning a value should throw SyntaxError

In light of the recent thread discussing async and await keywords, I thought it'd be appropriate to raise this point again, understanding it may be too late to make a change. As my original post details, the concept of `return` within a generator is surprising in its difference in behavior from

Re: Rename Number.prototype.clz to Math.clz

On 18 January 2014 06:25, Jason Orendorff jason.orendo...@gmail.com wrote: Except I think we want bitlen(0) === 0 for consistency with clz. Just noting that this actually works: Math.ceil(Math.log(0 + 1) / Math.LN2) === 0 However: Math.ceil(Math.log(-1 + 1) / Math.LN2) === -Infinity Not

Re: Object.is()

If anecdotal sharing is valuable... As a JS web developer, I'd say so. I use isNaN weekly, and have never once had to distinguish +/-0. It may be useful in some very limited cases, but for me Object.is would be much more valuable without it. Having the distinction means that in most cases I won't

Proposal: Generator returning a value should throw SyntaxError

Hi all, Long-time lurker, first-time poster. Profuse apologies if this was mentioned before and I failed to find it. I've been using V8's generator implementation in Node 0.11.x recently, and have come across what I believe is a footgun with generators currently. That is - the ability to return

Re: Proposal: Generator returning a value should throw SyntaxError

Thanks, I see. The usage is for TaskResult sorts of things where the scheduling is done via calls to `yield`, and the output of the function is done via `return`. Fair enough. It still seems like a huge footgun for the other cases which I'd expect are far more common than cooperative scheduling,