-
Notifications
You must be signed in to change notification settings - Fork 88
Use of NSDictionary and NSArray in Mappable protocol #80
Comments
Thanks for bringing this up! We have had the same conversation and the (tentative) plan is to move away from |
Thanks for your reply! I also think it is a good idea to schedule it with the Swift 3 release, since Swift 3 introduces a lot of breaking changes anyway. |
@mergesort can you remind me what issue you were seeing because of this? |
It wasn't an issue so much as annoyance that have to cast That said, I'm never going to say no to a pure Swift solution. 😄 |
The one thing currently stopping us from doing this is that the last time we checked (with Swift 1.0) the cost for bridging was significant. We'll have to do some simple benchmarks to see if this is still the case. If that is no longer a problem we will definitely change them! |
Any update regarding this? |
Contributions welcome! |
The
Mappable
protocol usesNSDictionary
andNSArray
in its convenience methods.Since Swift continues to move away from Objective C with 3.0, I would propose to change the types to
[String: Any]
and[Any]
/[[String: Any]]
so it integrates more naturally in Swift development. Or is there any good reason to preferNSDictionary
/NSArray
over these?The text was updated successfully, but these errors were encountered: