Re: const VS features detection

2014-01-06 Thread Brendan Eich
Allen Wirfs-Brock wrote: I had been considering purging that handling from the ES6 spec. but maybe I'll leave it in. Please do! This dates from block-lambda future-proofing days? I dimly recall ES1 drafts having full completion-type abstraction (over all forms, not just statements but also e

Re: const VS features detection

2014-01-06 Thread Allen Wirfs-Brock
On Jan 6, 2014, at 8:10 AM, Brendan Eich wrote: > David Herman wrote: >> On Dec 20, 2013, at 5:32 AM, Andreas Rossberg wrote: >> >>> > For ES7 I would like to revive the do-expression proposal (hopefully >>> > at the next meeting) >> >> Glad to hear you're in favor! I'll be happy to co-champ

Re: const VS features detection

2014-01-06 Thread Brendan Eich
David Herman wrote: On Jan 6, 2014, at 8:10 AM, Brendan Eich wrote: > To further constrain design (since design is mostly about leaving things out), I will address the ES4-era |let (x = y, z = z /* outer z*/) ...| let blocks and let expressions, which came up recently. We should not revive

Re: const VS features detection

2014-01-06 Thread David Herman
On Jan 6, 2014, at 8:10 AM, Brendan Eich wrote: > To further constrain design (since design is mostly about leaving things > out), I will address the ES4-era |let (x = y, z = z /* outer z*/) ...| let > blocks and let expressions, which came up recently. We should not revive > these, given do e

Re: const VS features detection

2014-01-06 Thread Brendan Eich
David Herman wrote: On Dec 20, 2013, at 5:32 AM, Andreas Rossberg wrote: > For ES7 I would like to revive the do-expression proposal (hopefully > at the next meeting) Glad to hear you're in favor! I'll be happy to co-champion. I will support your prospective championship ;-). To further

Re: const VS features detection

2014-01-06 Thread David Herman
On Dec 20, 2013, at 5:32 AM, Andreas Rossberg wrote: > For ES7 I would like to revive the do-expression proposal (hopefully > at the next meeting) Glad to hear you're in favor! I'll be happy to co-champion. The const-initializer use case is a good one, but it's also extremely valuable for code