domenic at domenicdenicola.com (2014-03-02T22:34:42.006Z)
I don't see the point of throwing an error when calling .next('foo') on
a newborn generator. We don't throw an error on .next('foo', 'bar'),
and unlike the case with most function calls there is no way to get the
'bar' when resuming a generator, as you don't have an arguments object.
I would punt on this issue entirely, and ideally remove the
"suspendedStart" state from the spec, renaming "suspendedYield" to
simply "suspended".
Just MHO :)
Hi, I don't see the point of throwing an error when calling .next('foo') on a newborn generator. We don't throw an error on .next('foo', 'bar'), and unlike the case with most function calls there is no way to get the 'bar' when resuming a generator, as you don't have an arguments object. I would punt on this issue entirely, and ideally remove the "suspendedStart" state from the spec, renaming "suspendedYield" to simply "suspended". Just MHO :) Andy