The Swift evolution process describes the process by which Swift evolves. This document tracks the currently active proposals in that process.
- January 6...8, 2016: SE-0010: Add StaticString.UnicodeScalarView
- January 22...February 5, 2016: SE-0023: API Design Guidelines
- January 22...February 5, 2016: SE-0006: Apply API Guidelines to the Standard Library
- January 22...February 5, 2016: SE-0005: Better Translation of Objective-C APIs Into Swift
- February 10...23, 2016: SE-0030: Property Behaviors
- February 11...15, 2016: SE-0031: Adjusting inout Declarations for Type Decoration
- February 11...16, 2016: SE-0027: Expose code unit initializers on String
- February 12...18, 2016: SE-0024: Optional Value Setter
??=
- February 16...19, 2016: SE-0035: Limiting
inoutcapture to@noescapecontexts - February 18...23, 2016: SE-0033: Import Objective-C Constants as Swift Types
- February 17...22, 2016: SE-0034: Disambiguating Line Control Statements from Debugging Identifiers
- SE-0012: Add
@noescapeto public library API - SE-0016: Adding initializers to Int and Uint to convert from UnsafePointer and UnsafeMutablePointer
- SE-0017: Change
Unmanagedto useUnsafePointer - SE-0025: Scoped Access Level
- SE-0026: Abstract classes and methods
- SE-0032: Add
findmethod toSequenceType - SE-0036: Requiring Leading Dot Prefixes for Enum Instance Member Implementations
- SE-0037: Clarify interaction between comments & operators