Don't forget the implications for the future. If declaring certain names in top level scopes is an error if they are also present in the global or host environment, it means that ES7+ can never define new names on the global (or HTML6+ can never define new names in the host environment) without risking hard errors in existing code. --scott
On Wed, Oct 29, 2014 at 2:58 PM, Allen Wirfs-Brock <[email protected]> wrote: > > On Oct 29, 2014, at 6:59 AM, Andreas Rossberg <[email protected]> wrote: > >> On 28 October 2014 17:38, Allen Wirfs-Brock <[email protected]> wrote: >>> Also I'll check if it's feasible to make it a runtime error for a global >>> let to shadow a non configurable property of the global object. >> >> Is there a reason why we cannot make it an error for any present >> property? Maybe that would even allow us to get rid of the VarNames >> list? > > Perhaps, there is a legacy that requires that var/function declarations can > over-write global object properties. There is no particular reason that we > have to allow this for let-like declarations. > > Allen > _______________________________________________ > 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
