changing behavior based on tick seems sketchy about co

[tj]

the main problem is that this path: https://github.com/visionmedia/co/blob/master/index.js#L80
is a lot faster than the else branch with setImmediate(), but that only really exists for composing co()s. I'm down for reworking that a bit, it would only damage the somewhat unrealistic use-case of co(function *(){}) with no callback

co(function *(){
  yield foo;
  yield bar;
  done();
})

would have to become:

co(function *(){
  yield foo;
  yield bar;
})(done);

// or 

co(function *(){
  yield foo;
  yield bar;
}, done);

// or

co(function *(){
  yield foo;
  yield bar;
  done();
})();

[matthewmueller]

I'm not sure exactly where done is coming from, but I think the last one makes the most sense. co would return a function (not sure if that's called a thunk) that takes an optional callback.

Yah, I think co(function *(){}) makes for nice examples but is pretty unrealistic. Even a pretty simple app I made to experiment quickly outgrew this use-case.

[tj]

yeah agreed!

[matthewmueller]

<333333333333