Is it impossible to tell if a function is a genera

2019-06-22 06:09发布

Looks like calling .bind(this) on any generator function breaks my ability to see if the function is a generator. Any ideas on how to fix this?

var isGenerator = function(fn) {
    if(!fn) {
        return false;
    }

    var isGenerator = false;

    // Faster method first
    // Calling .bind(this) causes fn.constructor.name to be 'Function'
    if(fn.constructor.name === 'GeneratorFunction') {
        isGenerator = true;
    }
    // Slower method second
    // Calling .bind(this) causes this test to fail
    else if(/^function\s*\*/.test(fn.toString())) {
        isGenerator = true;
    }

    return isGenerator;
}

var myGenerator = function*() {
}

var myBoundGenerator = myGenerator.bind(this);

isGenerator(myBoundGenerator); // false, should be true

3条回答
▲ chillily
2楼-- · 2019-06-22 06:30

This package has the solution:

https://www.npmjs.org/package/generator-bind

Basically, in order to get it to work you either need to polyfill Function.prototype.bind or call a custom bind() method.

查看更多
迷人小祖宗
3楼-- · 2019-06-22 06:44

Yes, it is possible to tell if a function is a generator even if .bind() has been called on it:

function testIsGen(f) {
  return Object.getPrototypeOf(f) === Object.getPrototypeOf(function*() {});
}
查看更多
Summer. ? 凉城
4楼-- · 2019-06-22 06:50

Since .bind() returns a new (stub) function that only just calls the original with .apply() in order to attach the proper this value, it is obviously no longer your generator and that is the source of your issue.

There is a solution in this node module: https://www.npmjs.org/package/generator-bind.

You can either use that module as is or see how they solve it (basically they make the new function that .bind() returns also be a generator).

查看更多
登录 后发表回答