Make our Swift better

on YouTube ↗13m

" summary

A concrete path for contributing to Swift: propose and implement Dictionary.compactMapValues into Swift 5, write unit tests and microbenchmarks, set up a 30-minute stdlib build to iterate, drive discussion on the Swift forums and address the core‑team API‑naming debate, fix migration pain by suppressing compiler warning 265 in real projects, and land the change with proposal accepted after months of review.

AI-written summary · about

" chapters (11)

1. 0:00Introduction and speaker intro
2. 1:49Switching from Objective-C to Swift
3. 3:19Community advice and improvements
4. 5:06Proposing new dictionary methods
5. 6:33Submitting a Swift proposal
6. 8:07Implementation and testing
7. 9:11Proposal review process
8. 9:55Proposal acceptance and Swift evolution
9. 10:41Contributing to Swift
10. 11:26Getting involved in Swift community
11. 12:28Closing remarks

" related talks

• 15mMake our Swift betterDaiki Matsudate · try! Swift NYC 2018
• 11mMaking our Swift betterDaiki Matsudate · AltConf 2019
• 33mContributing to Swift for the First TimeRobert Pieta · AltConf 2019
• 19mWhat's up with Swift 5Bas Broek · FrenchKit 2017
• 33mScaling Swift DevelopmentMarek Fořt · Swift Rockies 2026
• 57mCatching up with SwiftAsh Furrow · Philly ETE 2015
• 17mMigrate Swift 4.2 to 5.xShoMasegi · iOSDC Japan 2020
• 07mContributing to Swift CompilerYusuke Kita · try! Swift Tokyo 2019