I believe we already have a number of community-developed crypto libs for
Swift, the problem is not in the lib itself. The problem, as I see it, is
in one _choosen_ (and so, well-tested and supported by main team) that will
be brought into Swift. Yes, also don't think Swift team should create such
a new crypto lib from zero, some well-known lib imo will be better solution.
The question is - are there any plans in Swift team to provide "built-in"
crypto libs for Swift 3.0+ ?
On 13.04.2016 9:06, Brent Royal-Gordon via swift-evolution wrote:
It would seem to me that common crypto routines should become part of the core
Swift libraries without having to rely on unknown third party libraries or
bridging into the C based CommonCrypto lib.
This seems like a great candidate for a library that could be developed in the
community and then possibly brought into Corelibs in a future version, but I
strongly suspect it'll be considered out of scope for Swift 3.
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
