- Update submodules to eliminate new warnings, errors in Xcode 6.3b2.
- COpaquePointer.null() no longer available; instantiate with nil literal
instead.
- Fix warning when chaining optionals and optional casts.
- Update Guanaco, LlamaKit, Nimble, and Quick to versions that support
Swift 1.2.
- Update Xcode project and scheme files for "latest Xcode version"
parameters.
- Use Swift 1.2's new fallible casts for casts that may fail at runtime.
- Update Guanaco for improved matching on failures,
i.e.: `haveFailed(beAnError(domain: match("abc")))`.
- All functions that return Result objects now return sane errors for
failure cases.
- Unit tests verify libgit2 error is domain is used for most failures.
Guanaco provides Nimble assertions for LlamaKit.Result, such as:
```
expect(result).to(haveFailed(domain: "com.libgit2"))
```
These custom assertions will be useful when testing that libgit2 error
messages are properly captured and reported.
This is the first of a series of commits intended to resolve issue #10,
which calls for proper error handling.
One way to test that libgit2 error messages are being propagated through
Result failures is by asserting that the error's description or code
match the message or code we expect. In order to do so, LlamaKit's
ErrorType is unweildy, and not future-proof--it would be easier and
safer to write assertions based on NSError.
Upgrade LlamaKit to v0.5.0, the latest version that supports Swift 1.1,
in order to define results as type `Result<T, NSError>`.
