Evolution   Discussion


About the Discussion category (1)
Consistent lazy API (8)
Codable Improvements and Refinements ( 2 3 ) (40)
Swift for numeric programming (18)
Is it OK if the lazy version slightly differs in one parameter? (6)
Why are general collection returns fixed to Array? (8)
Swift is open-source but is it patent-free as well? (9)
Why are operators not available as static type members? (6)
Should a LazyMatchCollection be bi-directional when its base is? (1)
Why doesn't "reduce(into:)" include a variant that takes an "inout" input? (2)
@_exported and fixing import visibility ( 2 3 ) (51)
[Concurrency] async/await + actors ( 2 3 4 ) (71)
Revisiting the pointer conversions (14)
A RingBuffer collection (3)
More on rotate, Part 2 (4)
There's no way to channel a fail-able initializer to a throwing one, is there? (3)
Swift should not allow you to use "return" on an expression that doesn't return anything. This just leads to confusion when reading the code (3)
Enum implements `==` without being Equatable (5)
Can Swift be used to build a OS? (9)
A lazy version of Collection.split (9)
Lazy versions of Sequence.split (1)
Make class and struct members private by default / Type-Based access (6)
Inconsistant naming of unsafe "conversion" functions (2)
underestimatedCount on zip (10)
Value returning assignment operator (7)
Accepted, but not yet implemented SEs (2)
Is there a reason NSDecimalNumber is not Comparable? (4)
Should tuple equality operators work on tuples with different types? (9)
Swift as a cross-platform language and Windows support ( 2 3 4 ) (64)
Roadmap for and state of single element tuple types? ( 2 3 ) (42)