func-names: Allow unnamed generators (option)

What rule do you want to change? func-names

Does this change cause the rule to produce more or fewer warnings? Fewer

How will the change be implemented? (New option, new default behavior, etc.)? New option

Please provide some example code that this change will affect:

const parse = coroutinify(function* (input) { ... })

What does the rule currently do for this code? “Unexpected unnamed generator function” unless the option is set to "never"

What will the rule do after it’s changed? Allow unnamed generator functions if a second option is set to { generators: false } or similar

[joegoldbeck]

Sure, happy to clarify!

The reason comes down to language-level limitations, and in particular, that arrow notation can be used to create functions but not generators.

When we create lightweight functions, we use arrow notation, which are inherently unnamed. As one reference point, the AirBnb styleguide recommends this approach.

However, for generators, we can only use the standard function*, and so an exception for generators would allow us to create lightweight unnamed generators while leaving our stricter linting rules for functions intact.

[not-an-aardvark]

I see, thanks. That makes sense to me – let’s see if the rest of the team would be in favor of adding an option like this.