Alexander Schuch

I am quite busy at the moment, hence my late reply. Did you make sure `User` conforms to the `NSCoding` protocol? AwesomeCache uses the `NSCoding` protocol in order to persist...

I definitely plan to update the framework for the [`Codable`](https://developer.apple.com/documentation/swift/codable) protocol that will arrive with Swift 4. In the meantime, the only thing that comes to mind is actually casting...

Completion is also called if there is already a previously cached object. Are you sure there is no object called "name" in the cache already?

Sure you can. However, you'd probably want to create different instances of `Cache` for different kinds of content. Alternatively, you may create a `Cache` and serialize all you content to...

I guess you are using Cocoapods. There is no branch called "3.0.1" but you could try and use the "4.0" or "5.0" version tags.

Yes, the project will be updated to work with Swift 2.3 and 3.0 very soon.

The Swift 2.3 version is tagged as `4.0`, master contains a working Swift 3.0 version.

Yes, use tag `4.0` for Swift 2.3 and the master branch for Swift 3.0

Good idea. Do you want to give this a shot and submit a pull request?

Yes there is no way to get them all at the moment. Thanks for the suggestion, I'll keep it in mind for v3.0.