Similar but not the same. Within any given scope, a Type declared within that scope would need to be "set-in-stone" to be of any value. Furthermore, for a variable to honor that type, it must be able to carry around an unmodified reference to the tyoe as it existed at the time the variable was declared. If either one of these two conditions is not met, then the type system cannot claim to be static. It would be more of an "advisory" dynamic type system, where the specified type gives the engine a hint on what kind of data will be stored in a given variable.
On Fri, Apr 5, 2019 at 1:51 PM guest271314 <guest271...@gmail.com> wrote: > Similar concepts is not being able to re-declare a variable in any scope, > or a "Scope Controller" > > - Why does .then() chained to Promise.resolve() allow const declaration > to be reassigned? > <https://stackoverflow.com/questions/45380637/why-does-then-chained-to-promise-resolve-allow-const-declaration-to-be-reas> > > - > https://stackoverflow.com/questions/54776759/how-to-avoid-accidentally-implicitly-referring-to-properties-on-the-global-objec > > _______________________________________________ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
