ES6,ES7,ES8 and beyond. A Proposed Roadmap.

Sam Tobin-Hochstadt samth at ccs.neu.edu
Sun Apr 21 15:49:12 PDT 2013


Then consider `Object.freeze(console)`.

Fundamentally, frozen objects are not appropriate for prohibiting shared state.

Sam

On Sun, Apr 21, 2013 at 6:44 PM, Kevin Gadd <kevin.gadd at gmail.com> wrote:
> isn't typeof (console.log) "function" and not "object"? by object I meant an
> Object object, not 'any arbitrary JS value'. I suppose the distinction is
> really blurry, and you would still have to deal with problems like the
> object's prototype chain containing callables...
>
>
> On Sun, Apr 21, 2013 at 3:42 PM, Sam Tobin-Hochstadt <samth at ccs.neu.edu>
> wrote:
>>
>> On Sun, Apr 21, 2013 at 6:33 PM, Kevin Gadd <kevin.gadd at gmail.com> wrote:
>> > if I called Object.freeze or Object.seal on a JS object would it
>> > actually be
>> > safe to pass it to another thread and let both threads use it without
>> > any
>> > locking or guards?
>>
>> No, it's not safe.  Consider Object.freeze(console.log).
>>
>> Sam
>
>
>
>
> --
> -kg


More information about the es-discuss mailing list