Nimble v0.4.0

This version includes backwards-incompatible changes to support Swift 1.2. The
previous behavior of lazy evaluation of the argument in expect(...) has been
removed since Swift 1.2 no longer supports this. Use expect { ... } if you want
the lazy closure behavior.

Using toEventually() will check that this explicit closure is used and will
explicitly fail if the closure is not provided to expect.

Along with fixes for Swift 1.2, there are a few new features:

• Added beEmpty matcher for Objective-C.
• raiseException matcher can compare an exception's userInfo

Nimble v0.3.0

Changes in this release:

• Added waitUntil for Objective-C. Also waitUntilWithTimeout can be used with a custom timeout value. They work similarly to the swift versions:

  waitUntil(^(void (^done)(void) {
      // do a lot of work...
      done();
  });

• Added approximate equality (beCloseTo matcher) can use the ≈ operator. The operator can be easily typed with (option+x):

  expect(1.2) ≈ 1.2001

• Added approximate equality can also be given a delta with the ± operator (option + shift + =). This also works with the == operator, but still behaves like beCloseTo:

  // equivalent expectations
  expect(1.2) == 1.3 ± 0.5
  expect(1.2) ≈ 1.3 ± 0.5

• Added Nimble to Cocoapods Trunk. You no longer need to specify the :git keyword argument in your podfile. The prereleased version of cocoapods is still required.

Nimble 0.2.0

Changes in this release:

• Change: Objective-C matchers will now all properly reject nil values. Use beNil() to match against nils.
• Change: beEmpty() matcher no longer matches against nil
• Change: equal() uses Swift's built-in equality comparison.
• Change: Make objective-c matchers explicit about not accepting any arguments.
• Removed: Undocumented beOneOf() matcher that was Swift-only.
• New: expect().withTimeout() in objective-c for custom timeouts of async matchers.
• New: Added Podspec for Cocoapods' Swift Branch
• New: Documentation comments for Swift matchers
• New: NonNilMatcherFunc which supports emitting a consistent nil error message. Matchers that use this still need to safely process nils.