rejection/resolution of rejected/resoved promise must throw

[Gozala]

It could be that my expectations are just wrong, but I was assuming that resolving or rejecting a promise that was already resolved or rejected will throw exception. In any case here are the tests

http://github.com/kriskowal/q/pull/1#L4R62
http://github.com/kriskowal/q/pull/1#L4R97

In case behavior is expected we can change tests accordingly.

[kriskowal]

The behavior is expected; the idea is that promises need to be a uni-directional communication channel for security reasons. For example, a dozen consumers might be given the same resolver so that they can race to provide the resolution, but they should not be able to observe whether they won the race. That's what I heard from Tyler Close or Mark Miller anyway.

Thanks for the cases. I'll have more time to do integration for a while.

[Gozala]

Ok I'll update test cases accordingly and will include them into the pull request

[Gozala]

Fix in https://github.com/kriskowal/q/issues/#issue/7