Except that now I'm trying to follow the process for proposal as outlined in
the swift evolution docs.
Travis Beech | Principal Developer | Unwired Revolution
Optimizing Operations for Mobile and Distributed Systems
On Jun 13, 2016, at 5:02 PM, Brent Royal-Gordon wrote:
>> I’d like to pro
With the open sourcing of Swift and the growing concerns around security and
user privacy, Swift is lacking common crypto API’s as part of the core
libraries. I’d like to propose that we add common crypto functionality as part
of the Swift Core Libraries. I believe that something as important as
s part of the core library
Why would it need to be built into the language proper instead of the core
libraries? I am not too familiar with the core libraries, but perhaps
swift-corelibs-dev<https://lists.swift.org/mailman/listinfo/swift-corelibs-dev>
is the more appropriate mailing list her
the language proper instead of the core
libraries? I am not too familiar with the core libraries, but perhaps
swift-corelibs-dev<https://lists.swift.org/mailman/listinfo/swift-corelibs-dev>
is the more appropriate mailing list here?
On Apr 13, 2016, at 7:24 PM, Travis Beech via swift-evo
built into the language proper instead of the core
libraries? I am not too familiar with the core libraries, but perhaps
swift-corelibs-dev<https://lists.swift.org/mailman/listinfo/swift-corelibs-dev>
is the more appropriate mailing list here?
On Apr 13, 2016, at 7:24 PM, Travis Beech v
So what would it take to get a standard set of crypto API's built into the
language?
Travis Beech | Principal Developer | Unwired Revolution | c: 1 (209)
535-5357
Optimizing Operations for Mobile and Distributed Systems
On Apr 13, 2016, at 10:11 AM, David Waite
mailto:da...@alkaline-solu
So what are developers doing then to make sure their apps are secure? Are they
just not adopting Swift, or just relying on the bridging of CommonCrypto to
fill the gaps?
Travis Beech | Principal Developer | Unwired Revolution | c: 1 (209) 535-5357
Optimizing Operations for Mobile and Distributed
With the focus these days on writing secure applications it seems building this
functionality into the language would be pretty high on the list. These are
common API's found in modern languages and it would be nice to not have to use
hackish techniques like bridging into CommonCrypto to achieve
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.
Just some things off the top of my head that we should be able to do easily in
pure Swift is AES
