On Aug 31, 2013 6:20 PM, "Brendan Eich" <brendan at mozilla.com> wrote:
>
> Brian Kardell wrote:
>>
>>
>> Fwiw, just bikesheddingly speaking I actually prefer the *.
>>
>
> Let's review. Three reasons for function* syntax:
>
> 1. Opt-in required for backward-incompatible definition of 'yield' as
low-precedence unary prefix operator.
>
> 2. Zero-yield (no yield in body) basis case, useful for delegation via
yield* from another generator.
>
> 3. Decorator to alert the reader that the body contains yield (ignoring 2
for a moment) reason.
>
> You are "bikesheddingly" supporting 3, I take it. Can you say more about
why you want a decorator for human readers? Again ignoring 2, which makes
the case based on what the JS engine must see, a more "objective" criterion
in this case (and, in a different light, in case 1).
>
> /be

Yes.  I know its not especially useful and i debated sitting it out (as i
often do on this list) - i think #1 stands on it own, but I felt that there
was some debate about the value of #3 which isn't for compatibility or even
function but for developers, and perhaps it might be useful to say that
given the choice between * and none, I'd prefer the visual queue that tells
me its different with an easy scan because...It's bikesheddy - i know but I
thought it worth saying that as one of those devs I think it has value.  So
if we can get 1 and 3 with a single char... Win.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20130831/51344381/attachment.html>

On Aug 31, 2013 6:20 PM, "Brendan Eich" <brendan at mozilla.com> wrote:

> You are "bikesheddingly" supporting 3, I take it. Can you say more about why you want a decorator for human readers? Again ignoring 2, which makes the case based on what the JS engine must see, a more "objective" criterion in this case (and, in a different light, in case 1).

Yes.  I know its not especially useful and i debated sitting it out (as i
often do on this list) - i think #1 stands on it own, but I felt that there
was some debate about the value of #3 which isn't for compatibility or even
function but for developers, and perhaps it might be useful to say that
given the choice between * and none, I'd prefer the visual queue that tells
me its different with an easy scan because...It's bikesheddy - i know but I
thought it worth saying that as one of those devs I think it has value.  So
if we can get 1 and 3 with a single char... Win.