return when desugaring to closures
Mark S. Miller
erights at google.com
Sat Oct 11 16:17:17 PDT 2008
On Sat, Oct 11, 2008 at 4:01 PM, Brendan Eich <brendan at mozilla.com> wrote:
>> If we want to avoid the read-barrier, we should not hoist either const
>> or let. If we are to consider not hoisting const, WE NEED TO DECIDE
>> THIS NOW, before ES3.1 mandates a hoisting const.
> A few messages back you nicely repeated the
> least-concepts/least-astonishment/most-symmetric case for hoisting to block
> top that has carried so far. I don't see how we can backtrack here. We'll
> flail hard.
> [...other good stuff snipped...]
I'm convinced; thanks. I agree it's too late to consider non-hoisting
const even if we come to regret it. Given that const hoists, let
declarations must as well, and we can argue about let-read-barriers
and repeated declarations later.
More information about the Es-discuss