Evolution


Discussion The Evolution Discussion category is for general discussion of the evolution of the Swift language. Proposal Reviews This category is for posting Swift Evolution proposals for review and feedback. Announcements This category is for announcements of Swift evolution proposal reviews and results, as well as other administrative announcements. Creation of new topics in this category is by site admins and Swift Core Team members only, although anyone can reply to topics once created. Pitches The Pitches category is an area for pitching ideas for evolution of the Swift language prior to a formal review.
About the Evolution category [Evolution] (1)
SE-0240: Ordered Collection Diffing ( 2 ) [Proposal Reviews] (33)
SPM support for resources? [Discussion] (8)
Built-in unaligned loads [Pitches] (6)
Can property shadowing warnings be improved? (re: SR-6689) [Discussion] (12)
Key Path Expressions as Functions [Pitches] (20)
Why doesn't "reduce(into:)" include a variant that takes an "inout" input? [Discussion] (3)
Swift Pointer Syntatic Sugar [Pitches] (1)
Adaptation of C++'s std::search_n [Discussion] (1)
Sealed protocols ( 2 3 4 5 6 ) [Pitches] (106)
Codable Improvements and Refinements ( 2 3 ) [Discussion] (42)
Pitch: Reducing a sequence onto its own elements to simplify code and reduce errors ( 2 3 4 ) [Pitches] (64)
Trailing commas in all expression lists ( 2 ) [Pitches] (35)
Swift for numeric programming ( 2 ) [Discussion] (30)
Add `Float16` ( 2 ) [Pitches] (26)
Opaque result types ( 2 3 4 5 6 7 8 9 10 11 12 13 ) [Pitches] (247)
Default values for enum associated values [Pitches] (5)
Consistent lazy API [Discussion] (8)
Prepitch: Character integer literals ( 4 5 6 7 8 9 10 11 12 13 14 15 ) [Pitches] (296)
Is it OK if the lazy version slightly differs in one parameter? [Discussion] (6)
Why are general collection returns fixed to Array? [Discussion] (8)
Text streaming in standard library [Pitches] (11)
Remove implicit initialization of Optionals? [Pitches] (7)
Swift is open-source but is it patent-free as well? [Discussion] (9)
Uniquing collections efficiently [Pitches] (7)
Generalizing floating point math operators over the BinaryFloatingPoint protocol [Pitches] (8)
Swift should allow for suppression of warnings, especially those that come from Objective-C [Pitches] (15)
Why are operators not available as static type members? [Discussion] (6)
Add accumulate/scan to the standard library [Pitches] (3)
A More Swifty Way to Check an Optional for a Nil Value [Pitches] (19)