[swift-users] Secure Coding Guideline and SWIFT 3.0 release

Jens Alfke jens at mooseyard.com
Wed Aug 10 11:36:10 CDT 2016

> On Aug 10, 2016, at 4:30 AM, Pandey, Sunil Y via swift-users <swift-users at swift.org> wrote:
> 4.  Static analysis tool for Swift to check possible security issues

Keep in mind that the language itself is designed to prevent many of the errors that result in insecure code — dangling pointers, uninitialized variables, buffer overflows, arithmetic overflows…

(Yes, it’s still possible to commit some of those errors, but you have to go out of your way by using UnsafePointers or the unchecked arithmetic operators.)


More information about the swift-users mailing list