Feature request: configurable 'this' context about caf

[chrisregnier]

oh I didn't realize you could bind the context to the return runner! Didn't know if that would be safe in case the library tried to use 'this' at all for any of its own stuff.

But ya that'll totally work for me. Thanks

[getify]

So you're saying:

f = CAF(someobj.method, { context: someobj });

...instead of:

f = CAF(someobj.method.bind(someobj));

Did I miss something?

---

Also, as line 61 shows, the CAF wrapped function is this sensitive, so either manual or automatic this binding should still work:

someobj.method = CAF(someobj.method);

// later
someobj.method(token);

Or:

f = CAF(someobj.method);

// later
f.call(someobj, .. );

Or:

f = CAF(someobj.method).bind(someobj);

[chrisregnier]

Correct.
Using bind creates a new wrapping generator (and requires other support in older browsers)

someobj.method.bind(someobj)

whereas if you could pass in the context then CAF calls the generator function it could just set the context directly like this on line 194

gen.apply(context, args)