Re: Cancel Promise pattern (no cancellable promises)

2017-11-29 Thread Isiah Meadows
On Wed, Nov 29, 2017, 19:19 /#!/JoePea wrote: > Hello all, I'm posting here because I'm thinking about how not to leak > memory, and wondering if I am. > > Suppose I have an object that is cleaned up (GC'd), and that object's > constructor (for example) ran an anonymous function that listened to

Re: Toplevel 'let' binding can be left permanently uninitialized after an error

2017-11-29 Thread pacer...@gmail.com
TwiceMeta: Annul Previous till ThricePrevious. ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss

Re: Re: Toplevel 'let' binding can be left permanently uninitialized after an error

2017-11-29 Thread pacer...@gmail.com
Mmeta: Pparent edit code: This's subject is . On 29 November 2017 at 01:05, Joseph wrote: > You can still do `{x}`. ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss

Re: Toplevel 'let' binding can be left permanently uninitialized after an error

2017-11-29 Thread pacer...@gmail.com
TwiceMeta: FourfoldPrevious edit code: This's subject is . ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss

Re: Toplevel 'let' binding can be left permanently uninitialized after an error

2017-11-29 Thread pacer...@gmail.com
Mmeta: Pprevious edit code: This's subject is . ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss

Re: Toplevel 'let' binding can be left permanently uninitialized after an error

2017-11-29 Thread pacer...@gmail.com
Mmeta: TwicePrevious edit code: This's subject is . ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss

Re: Toplevel 'let' binding can be left permanently uninitialized after an error

2017-11-29 Thread pacer...@gmail.com
Mmeta: edit code: This's subject is . ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss

Toplevel 'let' binding can be left permanently uninitialized after an error

2017-11-29 Thread pacer...@gmail.com
Mmeta: edit code: This' a reply to . ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss

Re: Toplevel 'let' binding can be left permanently uninitialized after an error

2017-11-29 Thread pacer...@gmail.com
Mmeta: Pprevious edit code: This' a reply to . ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss

Re: Cancel Promise pattern (no cancellable promises)

2017-11-29 Thread /#!/JoePea
Hello all, I'm posting here because I'm thinking about how not to leak memory, and wondering if I am. Suppose I have an object that is cleaned up (GC'd), and that object's constructor (for example) ran an anonymous function that listened to a Promise. For exampel: ```js class Foo { constructor(

Re: Re: Toplevel 'let' binding can be left permanently uninitialized after an error

2017-11-29 Thread Jason Orendorff
On Wed, Nov 29, 2017 at 4:13 AM, pacer...@gmail.com wrote: > Re "..in subscope" and "..relevant"; As repl's can be fixed by > that---all snippets treated as curlybraced. > Hi everyone. For those of you who weren't on this list three years ago, here's the rest of the thread: https://esdiscuss.

Re: Re: Toplevel 'let' binding can be left permanently uninitialized after an error

2017-11-29 Thread pacer...@gmail.com
Re "..in subscope" and "..relevant"; As repl's can be fixed by that---all snippets treated as curlybraced. ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss