should contrib's wrap(..) pass-thru this binding?

[getify]

Right now, wrap(..) forces the this binding of its passed fn function to be ø (an empty DMZ object). So, if you need to wrap a this-aware function (aka "method"), you have to call .bind(..) yourself at time of wrapping:

var something = ASQ.wrap( obj.methodName.bind(obj) );

something(..);

If you forget, you lose your this binding, and things go bummer. Would it be less of a footgun if we passed through the this binding?

var something = ASQ.wrap( obj.methodName );
var something2 = ASQ.wrap( obj.methodName );

something(..); // fails
something.call(obj, ..); // works

something2 = something2.bind(obj);
something2(..); // works

obj.something = something;
obj.something(..); // works

Not sure if this feels better or more footgun'ish. It does preserve the flexibility to have an asynquence-wrapped function that can still be bound to another this later if needed.

---

I don't really want to complicate the API with another utility that handles this binding, but we could do this I guess:

var something = ASQ.wrap( obj.something, { this: obj } );

something(..); // works

Even something else we could do is make that binding be a "soft binding", where it defaults, but lets you override:

var something = ASQ.wrap( obj.something, { this: obj } );

something(..); // works against `obj`
something.call( obj2, .. ); // also works, but against `obj2`

That feels the most flexible and useful. But is it? Thoughts?