Skip to content

Tags: xianglibao/PromiseKit

Tags

5.0.0-alpha8

Toggle 5.0.0-alpha8's commit message

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
Update CoreLocation Extension

5.0.0-alpha7

Toggle 5.0.0-alpha7's commit message

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
Fix compiler order issue

5.0.0-alpha6

Toggle 5.0.0-alpha6's commit message

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
Fix verbose first.

4.1.8

Toggle 4.1.8's commit message

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
Tag 4.1.8

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.

4.1.7

Toggle 4.1.7's commit message

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
Silence Swift 3.1-beta warning

Tag 4.1.7

5.0.0-alpha3

Toggle 5.0.0-alpha3's commit message

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
Experiments with `flatMap`

5.0.0-alpha2

Toggle 5.0.0-alpha2's commit message

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
Second attempt at 5.0

5.0.0-alpha1

Toggle 5.0.0-alpha1's commit message

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
Experimental branch; changes follow:

* Fixes zalgo issues by always executing after at least one execution context
* Removes zalgo/waldo in favor of `nil` queue as per NSNotificationCenter etc.
* True zalgo behavior as per PMK<5 is now impossible (fix welcome) because even fulfill/reject must wait for the current execution context to expire
* All promise handlers take a Chainable return type now, reducing duplication and much reducing compiler mis-errors from Swift. Also making us basically more flexible. Ish. Because we now have to have a protocol extension for every type that can be implicitly returned. Sigh.
* Reduced duplication in AnyPromise/Promise by making core code a Mixin
* Error-Unhandler is temporarily removed, with Swift code it will *stay* removed as Swift is strict and Promise is strict and you get a warning if you don’t handle your error with Swift and if you ignore the warning you are asking for trouble. Instead always terminate your chains! We can’t be as strict in Objc and well, that’s why we like objc, so…
* Promise can no longer be derived. Which makes sense IMO.