On May 13, 2013, at 4:22 PM, Brendan Eich wrote: > Allen Wirfs-Brock wrote: >> In my response to Andy I concluded that syntactically restricting yield to >> not be finally protected is the better solution. > > It's a shame we have to around the block again. This was discussed over six > years ago, when we were prototyping for ES4 and studying Python 2.5. Python > started with that restriction and got rid of. So did we for ES4, prototyped > in SpiderMonkey and Rhino. > > But the rationale based on finally being a strong guarantee is just broken. > No such guarantee, so no need for 'close'. > > However (on top of a "But"), dropping close doesn't mean we should ban yield > in try.
Note I didn't propose no yield's inside of try's, only no yields in try's that include a finally clause. Allen _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
