Swift Unwrapped

Moving to Discourse, email from Ted: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170206/031657.html Nate Cook's Discourse experiment: http://discourse.natecook.com/ Slava tweets: https://twitter.com/slava_pestov/status/854490613575700480 https://twitter.com/slava_pestov/status/857382737669271552 Thank You Thanks to this episode's sponsor, Kobiton: complete mobile device lab solution. Start a 15 day free trial today at https://kobiton.com/swiftunwrapped.

Manifesto: https://github.com/apple/swift/blob/master/docs/OwnershipManifesto.md TL;DR: https://gist.github.com/Gankro/1f79fbf2a9776302a9d4c8c0097cc40e Graydon Hoare, Swift team member, creator of Rust: https://en.wikipedia.org/wiki/Rust_(programming_language) Some work has already landed to enforce exclusivity in Swift 4: https://github.com/apple/swift/pull/9373 https://github.com/apple/swift/pull/9198 https://github.com/apple/swift/pull/9112 Thank You Thanks to this episode's sponsor, BuddyBuild: a continuous integration, continuous deployment, and user feedback platform for iOS and Android development teams. Try it free today at https://www.buddybuild.com/.

SE-0168: Multi-line strings Proposal: https://github.com/apple/swift-evolution/blob/master/proposals/0168-multi-line-string-literals.md John Holdsworth (Injection4Xcode): https://twitter.com/Injection4Xcode Took just over 12 months to land: https://github.com/apple/swift/pull/2275 Final PR: https://github.com/apple/swift/pull/8813 Starter Bugs to improve diagnostics: https://bugs.swift.org/browse/SR-4701 Approval Post: https://lists.swift.org/pipermail/swift-evolution-announce/2017-April/000360.html Multi-line string literals in Objective-C: http://stackoverflow.com/questions/797318/how-to-split-a-string-literal-across-multiple-lines-in-c-objective-c #SE-0171: Reduce with inout https://github.com/apple/swift-evolution/blob/master/proposals/0171-reduce-with-inout.md Rationale: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170424/036126.html SE-0172: One-Sided Ranges https://github.com/apple/swift-evolution/blob/master/proposals/0172-one-sided-ranges.md Rationale: https://lists.swift.org/

String Manifesto: https://github.com/apple/swift/blob/master/docs/StringManifesto.md Chris Lattner on Swift 4 goals including String re-evaluation: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160725/025676.html Ole Begemann: Why String.CharacterView is not a MutableCollection: https://oleb.net/blog/2017/02/why-is-string-characterview-not-a-mutablecollection/ One for the Unicode Nerds: https://oleb.net/blog/2014/06/one-for-the-unicode-nerds/ Objc.io article on unicode: https://www.objc.io/issues/9-strings/unicode/ Unsafe API proposal: https://github.com/apple/swift/pull/7479 SipHash: https://github.com/apple/swift/blob/master/stdlib/public/core/SipHash.swift.gyb https://github.com/apple/swift/pull/4621 Thank You Thanks to this episode's sponsor, PerfectlySoft. Find tutorials and other content at http://perfect.org/learn.html

SE-0166: Swift Archival & Serialization NSCoding: https://developer.apple.com/reference/foundation/nscoding http://nshipster.com/nscoding/ Swift Archival & Serialization: https://github.com/apple/swift-evolution/blob/master/proposals/0166-swift-archival-serialization.md ABI Stability Dashboard: https://swift.org/abi-stability/ SE-0167: Swift Encoders https://github.com/apple/swift-evolution/blob/master/proposals/0167-swift-encoders.md Semantics of Codable Types in Archives NSValueTransformer https://developer.apple.com/reference/foundation/nsvaluetransformer http://nshipster.com/nsvaluetransformer/ "In the future, we may add API to allow Swift types to provide an Objective-C class to decode as, effectively allowing for user bridging across archival." Similar to Russ Bishop’s proposal Allow Swift types to provide custom Objective-C representations https://github.com/apple/swift-evolution/blob/master/proposals/0058-objectivecbridgeable.md Thank You Thanks to this episode's sponsor

Access Control Roller Coaster First came the private/fileprivate change (SE-0025): https://github.com/apple/swift-evolution/blob/master/proposals/0025-scoped-access-level.md Then came open (SE-0117): https://github.com/apple/swift-evolution/blob/master/proposals/0117-non-public-subclassable-by-default.md For the last few weeks, a faction in the community has been proposing undoing it (SE-0159): https://github.com/apple/swift-evolution/blob/master/proposals/0159-fix-private-access-levels.md Wow. Such email. Very list. https://twitter.com/swiftlybrief/status/846938309666492417 Rejection email: https://lists.swift.org/pipermail/swift-evolution-announce/2017-April/000337.html Doug Gregor opens discussion for expanding private: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170403/034903.html David Hart, with a new proposal from Doug’s suggestions: https://github.com/apple/swift-evolution/pull/668 http://www.jessesquires.com/thoughts-on-swift-access-control/ Modules Features shouldn't be des

Swift 3.1 Release Official Swift 3.1 release post: https://swift.org/blog/swift-3-1-released/ Swift 3.1 was first available on Swift for iPad, not macOS

There's been a much stronger focus on calling ObjC from Swift than the other way around, but in this talk we'll cover both directions and the parts of the Swift language involved in the process. ObjC Interop Overview Nikita Lutsenko's talk: https://realm.io/news/altconf-nikita-lutsenko-objc-swift-interoperability/ NS_SWIFT_NAME NS_SWIFT_UNAVAILABLE NS_REFINED_FOR_SWIFT NS_SWIFT_NOTHROW NS_NOESCAPE NSEXTENSIBLESTRING_ENUM Nullability Annotations Generic Annotations ClangImporter (omit needless words logic lives here) PrintAsObjC Kevin Ballard's PR to include unavailable/deprecated/availability attributes: https://github.com/apple/swift/pull/6480 ObjC codegen via string manipulation. Very hackable. Proposals on ObjC Interop Referencing ObjC key-paths: https://github.com/apple/swift-evolution/blob/master/proposals/0062-objc-keypaths.md Referencing ObjC property selectors: https://github.com/apple/swift-evolution/blob/master/proposals/0064-property-selectors.md Referencing ObjC selector of a method: http

Swift has evolved since 1.x to have a fluctuating amount of magic/implicit bridging from ObjC and Foundation types, sometimes going in the opposite direction towards very explicit type conversions. We've started seeing more of what the "steady state" looks like as Swift 3.x/4.x development matures. In the early days, Swift users would need deep compiler internal implementation details to know which NSNumber-representable type could implicitly convert. As of SE-0139 that's a lot clearer. The subtleties of unenforced protocol conformance semantics: https://oleb.net/blog/2016/12/protocols-have-semantics/ Proposals on bridging New from Doug Gregor, limiting @objc inference: https://github.com/DougGregor/swift-evolution/blob/objc-inference/proposals/NNNN-objc-inference.md NSNumber and NSValue: https://github.com/apple/swift-evolution/blob/master/proposals/0139-bridge-nsnumber-and-nsvalue.md Optional to payload or NSNull: https://github.com/apple/swift-evolution/blob/master/proposals/0140-bridge-optional

Every Swift developer who has migrated code bases from Swift 1.x to 2.x, or even the more tedious 2.x to 3.x knows the pain of migrating to new Swift versions. In this episode, we cover: What is a source breaking change? Almost guaranteeing that code that compiles with Swift 3.0 continues to compile with Swift 3.x and even Swift 4.x in Swift 3 mode. Why almost? Because it may be best to prevent code that never should have compiled with Swift 3.0 (i.e. compiled due to egregious bugs in the compiler) from compiling as those bugs are fixed. There are times when breaking compilation is preferable to continuing to exploit Swift bugs. "we should try to get the “rearrange all the deckchairs” changes into Swift 3 if possible, to make Swift 3 to 4 as smooth as possible": https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160125/007737.html Community-driven breakage ;) Slava Pestov (@slava_pestov) found and fixed a 'horrific' Swift 3 compatibility bug. When they say Swift 3.1 will be compatible

In this episode, we dive into the framework we love to hate to love: SourceKit. We wrap up with an overview of method dispatch in Swift. SourceKit on Linux Swift core team is fixing compiler crashers faster than they're filed! Slava Pestov being a driving force behind many of these fixes. @practicalswift is basically Swift compiler fuzzing as-a-service ;) Undoing all of @practicalswift's hard work SourceKit home page Process Isolation Key contributors to SourceKit: Brian Croom and his many SourceKit PRs to help get it linking and compiling on Linux. Alex Blewitt and his numerous attempts at getting SourceKit compiling by default on Linux. SR-1676: Build SourceKit on Linux CMake homepage swift-corelibs-libdispatch Final PR to get SourceKit building on Linux: #5903 CODE_OWNERS.TXT Jesse's talk at "try! Swift": Contributing to Open Source Swift Atom Editor Nuclide Atom Package Sourcery codegen tool Method Dispatch Raizlabs' article on Method Dispatch in Swift Chris Lattner's tweet about the ar

In this episode we take a look at the first full year of open source Swift development and the first complete release cycle (for 3.0) that happened completely in the open. We reflect on where we've been and how we got here. We discuss the initial launch, Swift evolution, the "Great Swift 3 Migration", and more! Open source announcement First Swift.org blog post First issue of Swift Weekly Brief First commit to Swift Core Team Swift Evolution proposals SE-0081: Move where clause to end of declaration SE-0004: Remove the ++ and -- operators SE-0007: Remove C-style for-loops with conditions and incrementers Email: Winding down the Swift 3 release Change to Swift 3 goals Email: End of source-breaking changes for Swift 3 Generics Manifesto ABI Stability Manifesto Swift 2 to Swift 3 migration guide Tooling: SourceKit Ryan Olson, Is Apple Using Swift in iOS?, (Hacker News) Swift Package Manager Swift Playgrounds for iPad

There are tons of podcasts out there about general Apple/iOS/macOS development but nothing specifically about only the Swift programming language. So, we decided to make a podcast about the Swift language and a commentary on the Swift Weekly Brief. This podcast is a continuation on more details about Swift Weekly and our own thoughts on Swift news. If you want to connect with us you can find us and reach out on twitter: JP Simard & Jesse Squires Be sure to subscribe so you don't miss episode 01 - airing on Monday, March 6th and be sure to check out some of the other development shows that are a part of the Spec Network.