Why GeneratorFunction constructor isn't directly exposed to end users?

# Michał Wadas (9 years ago)

It could be either Function property or new global object...

It could be either Function property or new global object...

# Allen Wirfs-Brock (9 years ago)

On Feb 28, 2015, at 2:20 PM, Michał Wadas wrote:

It could be either Function property or new global object...

Or an import from a standard module.

It wasn't directly exposed in ES6 was because it lacked strong use cases and we didn't want to clutter up the global namespace with something of little value. Particularly, with module imports becoming available as an alternative to new globals.

On Feb 28, 2015, at 2:20 PM, Michał Wadas wrote:

> It could be either Function property or new global object...

Or an import from a standard module.

It wasn't directly exposed in ES6 was because it lacked strong use cases and we didn't want to clutter up the global namespace with something of little value.  Particularly, with module imports becoming available as an alternative to new globals.

Allen