Add async expectations "will" and "willNot`

- Overload "expect" DSL to take a closure and return a closure "actual"
- Closure actuals respond to "will" and "willNot", returning asynchronous
  expectation objects
- Async expectations repeatedly evaluate the closure before timing out.
- Currently, matchers must extend both regular and asynchronous matchers.
  This is a design flaw which should be fixed.
README: add section on expectations
README: refer to example project
Remove "isConcreteSpec" function

Since `QuickSpec` isn't included in the test cases of any
project its linked with, it's no longer necessary to determine
which test cases are "concrete" before returning example groups.
FunctionalTests: fix typo
README: show off async more prominently
Report file, line number along with failures

- Use callsite structs to pass references to the file and line
  number associated with an expectation.
- Have World keep track of the currently executing example.
- Have Example maintain a weak reference to its current test case.
  This allows Expectation to message that test case regarding failures.
  Note that this couples QuickExpectations to QuickCore. This is an
  architecture regression that should be addressed in the near future.

This commit is an improvement, but it still doesn't resolve issue #7.
Although failures are reported, causing the test suite to fail, Xcode
only displays a red line and failure message at the callsite for a
split-second, then the message disappears.
Use XCTFail instead of XCTestCase failure reporting

When using XCTest in Swift, we have access to an *awesome* function
called `XCTFail`, which allows us to report failures without a reference
to the current test case. Use `XCTFail` to break the coupling between
QuickCore.World and QuickExpectations.
README: add screenshot
Quick is the 1st BDD framework to support Xcode 6

This fixes issue #1: Xcode test navigator integration.

As of Xcode 6, each test invocation's selector is used to determine the
name displayed in the test navigator. Specta and Quick both used the
same instance method (`-[QuickSpec runExampleAtIndex:]`, in Quick's
case) to run each example. As a result, all tests in the same spec had
the same name, causing each example to "overwrite" each previous one in
the navigator. This caused several issues, including red lines to
indicate test failure in Xcode suddenly disappearing when the next
example finished running.

During `+[QuickSpec testInvocations]`, define a new instance method for
each example. Then, return an invocation that executes that new instance
method
QuickSpec: remove unused method
Stub before/afterSuite and add two failing specs
Implement beforeSuite and afterSuite
Equal: add spec

Addresses #12.
Contain: flatten failure messages

Failure messages for collections would span multiple lines, which did
not display correctly in Xcode.

Addresses #12.
BeTrue: add spec

Fixes issue #12.
Add Prediction; matchers extend Prediction
README: update screenshot
README: add plea for help
Remove unnecessary bridging header