Failure to handle promise that is resolved before promise is returned

[derrickburns]

One problem with using event emitters as promises is that there is no way to find out if an event has been emitted already or not. So, using an event emitter as a promise is problemmatic if the promise has been fulfilled prior to the return from the execution of the topic, i.e. the asynchronous code is actually executed synchronously.

[dunkfordyce]

this has just bitten me also. it would be better a "proper" promise ( like jquery Deferred or any of the commonjs promise types ) was used.

[indexzero]

This is really a documentation bug. We don't have promises per-se, this is actually a left-over from when node did have promises for a very brief period of time in 2010.

We should update our code to be "emitter" everywhere.

[indexzero]

Added the website tag because the vowsjs.org website has "promise" in a lot of example code.

[indexzero]

Fixed in 73872a8. Will open a corresponding bug on the website.

[ghost]

is it possible to add an example to the docs that show how one would use Vows.js with a promise-library such as Bluebird? I've tried to use Bluebird's asCallback functionality which kinda works, but there's also the EventEmitter strategy that Vows.js provides but I'm not sure how it would fit in with promises.

Thanks for the work you've done on this library, it's been really helpful!