Swift [and the] Evolution
- 3. "… fully span the gamut of programming:…"
- 4. "from wri)ng the lowest level firmware…"
- 5. "up to the highest level applica0on programming." -- Chris La8ner
- 6. Timeline
- 8. Goals for 2.2 • Quality-of-implementa0on improvements • Finishing touches on 2.0 features • Addi0ve (non-breaking) changes • No fundamental changes to SwiE's use • Depreca0ons in prepara0on for 3.0
- 9. Implemented proposals for Swi2 2.2 • Allow (most) keywords as argument labels (SE-0001) • Tuple comparison operators (SE-0015) • Constraining AnySequence.init (SE-0014) • Replace typealias keyword with associatedtype for associated type declaraEons (SE-0011) • Naming FuncEons with Argument Labels (SE-0021)
- 10. Accepted proposals for Swi1 2.2 • Add a Lazy flatMap for Sequences of Op8onals (SE-0008) • SwiB Language Version Build Configura8on (SE-0020) • Referencing the Objec8ve-C selector of a method (SE-0022)
- 12. Out of scope in 3.0 • Full source compa.bility • Concurrency • C++ interop • Hygenic macros • New major library func.onality
- 13. Goals for in 3.0 • Stable ABI + Resilience • Portability • Type system cleanup • Complete generics • Focus and refinement • API design guidelines
- 14. Care and Maintenance of Our New Programming Language
- 15. Use the language
- 16. "You can only test it by looking at a large enough body of code and seeing what problems they face." — Chris La*ner
- 17. Give what you can
- 19. Be willing to reframe your concern
- 20. The Core Team spends .me we don't 'see' We had extensive internal discussions about proper4es, and made substan4al progress, but we do not yet have wording suitable for the guidelines. Let me tell you where things stand. — Dave Abrahams
- 21. Swi$ has a history
- 22. Time is a finite resource
- 23. • Use Swi) • Research • Don't hesitate
- 24. Swi$ is Young