Re: [swift-evolution] Introducing synthesized locks

It's relatively unlikely that Swift's concurrency model, once it gains one, will look all that similar to Objective-C's. For example*, if Swift were to adopt a shared-nothing model where heap storage was per-thread and could only be accessed by another thread by copying or moving the value to

Re: [swift-evolution] [Returned for revision] SE-0161: Smart KeyPaths: Better Key-Value Coding for Swift

The rationale for using the same syntax is that a KeyPath is an unapplied property/subscript access. Even the multi-segment part of it isn't necessarily dissimilar: I don't think it would be unreasonable to imagine that \Foo.someMethod.someOtherMethod could work*, that'd just be function

Re: [swift-evolution] Smart KeyPaths

> On Mar 20, 2017, at 4:12 AM, David Hart via swift-evolution > wrote: > > > >> On 20 Mar 2017, at 10:39, Jonathan Hull via swift-evolution >> wrote: >> >> +1. This is my favorite solution so far. >> >> With ‘Person.keypath.name' it

Re: [swift-evolution] Smart KeyPaths

> On Mar 17, 2017, at 3:08 PM, Matthew Johnson via swift-evolution > wrote: > >> >> On Mar 17, 2017, at 12:04 PM, Michael LeHew via swift-evolution >> > wrote: >> >> Hi friendly swift-evolution folks, >>

Re: [swift-evolution] Smart KeyPaths

> On Mar 17, 2017, at 12:34 PM, David Hart via swift-evolution > wrote: > > Sent off-list by mistake: > > Nice proposal. I have a few comments inline: > >> On 17 Mar 2017, at 18:04, Michael LeHew via swift-evolution >>

Re: [swift-evolution] [Pitch] Support for pure functions. Part n + 1.

> On Feb 20, 2017, at 2:56 PM, David Sweeris via swift-evolution > wrote: > >> >> On Feb 20, 2017, at 2:50 PM, Michel Fortin via swift-evolution >> wrote: >> >>> Le 20 févr. 2017 à 14:45, Matthew Johnson a écrit

Re: [swift-evolution] [Pitch] consistent public access modifiers

> On Feb 15, 2017, at 10:57 PM, Rien wrote: > > > >> On 16 Feb 2017, at 03:45, David Smith wrote: >> >>> >>> On Feb 15, 2017, at 8:35 AM, Rien via swift-evolution >>> wrote: >>> On 15 Feb 2017, at 17:02,

Re: [swift-evolution] [Pitch] consistent public access modifiers

> On Feb 15, 2017, at 8:35 AM, Rien via swift-evolution > wrote: > >> >> On 15 Feb 2017, at 17:02, Matthew Johnson wrote: >> >>> >>> On Feb 15, 2017, at 9:59 AM, Rien wrote: >>> On 15 Feb 2017, at 16:45,

Re: [swift-evolution] Pitch: Replacement for FileHandle

> On Feb 14, 2017, at 7:18 AM, Charles Srstka via swift-evolution > wrote: > > MOTIVATION: > > In Swift 3, NSFileHandle was renamed to FileHandle, making it the de facto > file handle class for use in Swift applications. Unfortunately, it’s not a > very good API.

Re: [swift-evolution] Subclass Existentials

> On Feb 2, 2017, at 11:20 AM, Douglas Gregor via swift-evolution > wrote: > > >> On Feb 1, 2017, at 11:44 PM, Adrian Zubarev > > wrote: >> >> typealias AnyObject = … is nice to have, but

Re: [swift-evolution] Dropping NS Prefix in Foundation

> On May 7, 2016, at 11:37 AM, Patrick Smith via swift-evolution > wrote: > > I think everyone possibly has different definitions of what ‘Swift-native > rethinking’ could involve? My thoughts are, the Swift standard library is a > base library of types and