This is _super_ annoying, but Xcode kept yelling at me about needing to
update Curry to the latest syntax. After updating the version here,
Xcode will shut the hell up about it.
Instead of declaring Runes as a public dependency, we should declare it
as a private dependency and only use it for the operator definitions. We
will use Carthage to manage it as a git submodule.
We don't actually need to be so prescriptive about what version of Runes
we're using anymore. Any version after we turned on extension
compatibility will be fine for our needs.
This solves a couple of issues:
1. Users that pass `--no-build --use-submodules` can now use Argo
without running into errors from missing framework search paths
(fixes#121)
2. Users that want to use Submodules as a dependency management solution
can now do so without having to jump through any additional hoops.
We're still going to use Carthage as a development dependency, but it's
going to act as a semantic wrapper around submodules, instead of relying
on the binaries.
Including these directly in Argo could lead to compilation issues if
they were also defined somewhere else. Instead, it probably makes more
sense to extract them to a common dependency, and then rely on them.
This way, other users can simply import the same framework and we don't
have to worry about conflicts.
Note that since we're including this new dependency, we now have to
check in the `Carthage/Checkouts` folder in order to get everything to build
properly in client applications.
We will also need to add Runes to CocoaPods in order to be able to bump
the Podspec version.
