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 here?
> On Apr 13, 2016, at 7:24 PM, Travis Beech via swift-evolution > <swift-evolution@swift.org> wrote: > > 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 <da...@alkaline-solutions.com > <mailto:da...@alkaline-solutions.com>> wrote: > >> I don’t know if we need a boost-like parent project in order to start >> building core code to be brought for inclusion. >> >> I think success will naturally bring such a project structure - people >> seeking a curated and integrated set of frameworks to get common >> functionality. >> >> -DW >> >>> On Apr 13, 2016, at 12:16 PM, Tino Heth via swift-evolution >>> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: >>> >>>> 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 >>> true — but sadly, there seems to be either no interest or manpower for a >>> boost-like infrastructure… >>> Like many other fundamental topics, I don't think crypto belongs to the >>> stdlib, but none the less, there should be a standard library for >>> encryption/hashing. >>> _______________________________________________ >> > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
