The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days.
# New Features
- Optional, faster-compiling alternatives to equality operators have been added (`/==/`, `/<=/`, `/>=/`). See #93 for details.
# New Features
- Swift Package Manager support #86 (thanks @ZevEisenberg!)
- Runs tests using Xcode 11 for Swift 4.2 and 5.0
# Deprecations
- Drops official support for Xcode 10.x and Swift 4.0, although they should still continue to work.
See [all commits since 4.3.1](https://github.com/Rightpoint/Anchorage/compare/4.3.1...4.4.0).
# New Features
- Full support for Xcode 10.2 and Swift 5.0
# Deprecations
- Drops official support for Xcode 9.x
See [all commits since 4.3](https://github.com/Rightpoint/Anchorage/compare/4.3...4.3.1).
# New Features
- Full support for Xcode 10 and Swift 4.2 (#62, @heyltsjay)
See [all commits since 4.2.3](https://github.com/Raizlabs/Anchorage/compare/4.2.3...4.2.4).
# Bug Fixes
- Allow construction of an `AnchorPair` outside of Anchorage. (#59, @ZevEisenberg)
- Note: this change is non-breaking, but to realize its benefits, you may need to delete code like this if you had added it to your project:
```swift
extension AnchorPair {
init(first: T, second: U) {
self.first = first
self.second = second
}
}
```
See [all commits since 4.2.2](https://github.com/Raizlabs/Anchorage/compare/4.2.2...4.2.3).
# Bug Fixes
- Added support for building with Swift 4.2 in Xcode 10. (#60, @kabiroberai)
See [all commits since 4.2.1](https://github.com/Raizlabs/Anchorage/compare/4.2.1...4.2.2).
# Bug Fixes
- Updated to Swift 4.1 and Xcode 9 (#56, @irace)
- Started building on CircleCI 2.0 (#57, @ZevEisenberg)
- Added support for nested batches, thanks to @sanekgusev (#52)
- Add support for multiplier constraints derived from axis, thanks to @sanekgusev
Anchorage 4.1 adds support for Xcode 9, iOS 11, tvOS 11, and macOS 10.13.
This version also drops support for `Float80`. If you were previously using this floating-point type in UI code, you may want to... reconsider.