For discussion: should resolving a deferred more than once raise an exception? about deferred HOT 7 CLOSED

That sounds like a good idea. I wonder if an exception or warning would be better?

from deferred.

How about this?

f06157e

from deferred.

I saw this in the "Exception Programming Topics" guide (https://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/Exceptions/Exceptions.html):

You should reserve the use of exceptions for programming or unexpected runtime errors such as out-of-bounds collection access, attempts to mutate immutable objects, sending an invalid message, and losing the connection to the window server. You usually take care of these sorts of errors with exceptions when an application is being created rather than at runtime.

A promise should be immutable after being fulfilled, so an exception seems appropriate.

from deferred.

Sounds great to me. I also like your spec technique of registering an assertion handler. I haven't run your specs but I assume this keeps the output clean?

On Tue, Aug 19, 2014 at 11:37 AM, Kurtis Seebaldt
[email protected] wrote:

I saw this in the "Exception Programming Topics" guide (https://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/Exceptions/Exceptions.html):
You should reserve the use of exceptions for programming or unexpected runtime errors such as out-of-bounds collection access, attempts to mutate immutable objects, sending an invalid message, and losing the connection to the window server. You usually take care of these sorts of errors with exceptions when an application is being created rather than at runtime.

A promise should be immutable after being fulfilled, so an exception seems appropriate.

Reply to this email directly or view it on GitHub:
#24 (comment)

from deferred.

Yeah, the assertion handler keeps the NSAssert log message from appearing.

from deferred.

I like this f06157e - what do you think about merging it in?

from deferred.

done

from deferred.