Re: Re: standardizing Error.stack or equivalent

2014-04-15 Thread Christoph Martens
Hey guys, I wanted to chime in on the discussion about Error.stack standardization. For my lil' game engine (http://lycheejs.org) I tried a couple things out how a custom Debugger (for a binary WebSocket protocol) can be implemented properly. I need to write an own debugger, because I'm using

Re: Exceptional exits from generators

2014-04-15 Thread Andy Wingo
Hi, A re-ping on this issue. Probably the relevant people were distracted by TC39 last week. On Tue 08 Apr 2014 14:47, Andy Wingo wi...@igalia.com writes: Hello, The current ES6 draft seems to specify that if a running generator throws an exception, that its state moves to completed. It

Re: April 10 2014 Meeting Notes

2014-04-15 Thread Andreas Rossberg
## Revisiting: Generator Issues (Jafar Husain) [...] JH: The crucial problem: the iterator claims to be an iterable and it's not. ...If async generators return Iterables, not Iterators. WH: How JH: If I accept an iterable and invoke `@@iterator`, I would expect to get a fresh iterator

Re: Exceptional exits from generators

2014-04-15 Thread Allen Wirfs-Brock
yes, It's on my get back to soon list... Allen On Apr 14, 2014, at 12:36 AM, Andy Wingo wrote: Hi, A re-ping on this issue. Probably the relevant people were distracted by TC39 last week. On Tue 08 Apr 2014 14:47, Andy Wingo wi...@igalia.com writes: Hello, The current ES6 draft

Decorators vs Annotations (was April 10 2014 Meeting Notes)

2014-04-15 Thread Erik Arvidsson
On Tue Apr 15 2014 at 10:27:23 AM, Rick Waldron waldron.r...@gmail.com wrote: ## Decorators for ES7 (Yehuda Katz) Slides: (need slides) YK: Presenting aspects of common use cases not yet covered by ES6 `class`. Knockout.js example (compute the value of a property) WH: Do you want to

Re: April 10 2014 Meeting Notes

2014-04-15 Thread Allen Wirfs-Brock
On Apr 15, 2014, at 8:24 AM, Andreas Rossberg wrote: Proposal: - for...of always assume generator creation - for...of alwayss terminates generator function Lost in cross talk... NM: If you know that iterable creates a fresh iterator, it's very reasonable to close it every

Re: Exceptional exits from generators

2014-04-15 Thread C. Scott Ananian
+1 from me. I thought through the issue and your proposal seems to make sense. --scott ___ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss

RE: Decorators vs Annotations (was April 10 2014 Meeting Notes)

2014-04-15 Thread Ron Buckton
-Original Message- From: Erik Arvidsson [mailto:erik.arvids...@gmail.com] Sent: Tuesday, April 15, 2014 8:38 AM To: waldron.r...@gmail.com; es-discuss@mozilla.org; Yehuda Katz Cc: Ron Buckton Subject: Decorators vs Annotations (was April 10 2014 Meeting Notes) On Tue Apr 15 2014

Re: Exceptional exits from generators

2014-04-15 Thread Allen Wirfs-Brock
It woulds also be good to create a bugs.ecmascript.org ticket for this. That will ensure it doesn't get lost Allen On Apr 15, 2014, at 8:25 AM, Allen Wirfs-Brock wrote: yes, It's on my get back to soon list... Allen On Apr 14, 2014, at 12:36 AM, Andy Wingo wrote: Hi, A re-ping on

Re: Exceptional exits from generators

2014-04-15 Thread Jason Orendorff
On Tue, Apr 8, 2014 at 7:47 AM, Andy Wingo wi...@igalia.com wrote: iter.next() // = { value: undefined, done: true } I find this very strange. I would have expected an exception of the kind generator is already running, as indeed we entered the running state but never moved out of that

Realm API and this != global

2014-04-15 Thread Anne van Kesteren
Given that we now expose realms to JavaScript, fixing this mismatch between HTML and JavaScript seems somewhat more important (although really, HTML explicitly overriding JavaScript should be a big warning sign): https://bugs.ecmascript.org/show_bug.cgi?id=1898 Otherwise, the Realm API cannot