This proposal proposes to change the SSWG incubation process. The SSWG ask for the communities thoughts about this change.
- author: Johannes Weiss (@johannesweiss)
- feedback period: 2019-08-15 ..< 2019-08-29
*Unsafe* in Swift, Swift becomes as "safe" as C(++). Research shows that about 70% of the security vulnerabilities are related to memory unsafety.
Swift and SwiftNIO try to offer programmers fast and safe APIs which should mostly make the use of
*Unsafe* constructs unnecessary. If that is not the case, we appreciate feature requests to add API allowing to use safe APIs to the respective projects.
Add a bullet that says
*Unsafe* only if absolutely necessary.
Concrete wording update (in "Conventions and Style"):
- Does not use
*Unsafe*unless interfacing with C
- Exceptions to uses of
*Unsafe*constructs are tolerated if appropriately documented why they are absolutely necessary
*Unsafe*is used in this manner, it would be appreciated for feature requests to be made for Swift or SwiftNIO in order to make the use of the
More secure software in the SSWG.