Re: [swift-evolution] [Manifesto] Ownership

> On Mar 7, 2017, at 1:28 PM, jaden.gel...@gmail.com wrote: > On Mar 7, 2017, at 10:02 AM, John McCall via swift-evolution > > wrote: > >>> On Mar 7, 2017, at 11:47 AM, plx via swift-evolution >>>

Re: [swift-evolution] [Manifesto] Ownership

> On Mar 7, 2017, at 10:02 AM, John McCall via swift-evolution > wrote: > >>> On Mar 7, 2017, at 11:47 AM, plx via swift-evolution >>> wrote: On Feb 27, 2017, at 11:08 AM, John McCall wrote: On Feb

Re: [swift-evolution] [Manifesto] Ownership

> On Mar 7, 2017, at 11:47 AM, plx via swift-evolution > wrote: >> On Feb 27, 2017, at 11:08 AM, John McCall > > wrote: >> >>> On Feb 25, 2017, at 11:41 AM, plx via swift-evolution >>>

Re: [swift-evolution] [Manifesto] Ownership

> On Feb 27, 2017, at 11:08 AM, John McCall wrote: > >> On Feb 25, 2017, at 11:41 AM, plx via swift-evolution >> > wrote: >> 1: Collection Composition >> >> As much as the high-level picture is focused on safety,

Re: [swift-evolution] [Manifesto] Ownership

> On 7 Mar 2017, at 02:12, Karl Wagner wrote: > > >> On 6 Mar 2017, at 22:30, Dave Abrahams via swift-evolution >> wrote: >> >> >> on Mon Mar 06 2017, John McCall wrote: >> On Mar 6, 2017, at 3:46 PM,

Re: [swift-evolution] [Manifesto] Ownership

on Mon Mar 06 2017, Karl Wagner wrote: >> On 6 Mar 2017, at 22:30, Dave Abrahams via swift-evolution >> wrote: >> >> >> on Mon Mar 06 2017, John McCall wrote: >> > On Mar 6, 2017, at 3:46 PM, Karl Wagner

Re: [swift-evolution] [Manifesto] Ownership

> On 6 Mar 2017, at 22:30, Dave Abrahams via swift-evolution > wrote: > > > on Mon Mar 06 2017, John McCall wrote: > >>> On Mar 6, 2017, at 3:46 PM, Karl Wagner >>> wrote: >>> Thanks

Re: [swift-evolution] [Manifesto] Ownership

I ran into this exact issue today. Would something like inout returns help to fix it? I have a struct called StyledString which gets rid of much of the frustration of dealing with NSAttributedStrings in Swift. Basically, you make selections on the string and set some property of it like so:

Re: [swift-evolution] [Manifesto] Ownership

> On 6 mars 2017, at 15:53, John McCall via swift-evolution > wrote: > > Class types have reference semantics and are still copyable; ownership is not > going to change that. More generally, I don't see how anything we can do in > ownership could ever do something

Re: [swift-evolution] [Manifesto] Ownership

> On Mar 6, 2017, at 4:30 PM, Dave Abrahams via swift-evolution > wrote: > on Mon Mar 06 2017, John McCall wrote: > >>> On Mar 6, 2017, at 3:46 PM, Karl Wagner >>> wrote: >>> Thanks very

Re: [swift-evolution] [Manifesto] Ownership

on Mon Mar 06 2017, John McCall wrote: >> On Mar 6, 2017, at 3:46 PM, Karl Wagner >> wrote: >> Thanks very much for writing this up, it’s very interesting. >> >> The one thing which I think needs improvement is the

Re: [swift-evolution] [Manifesto] Ownership

> On Mar 6, 2017, at 3:46 PM, Karl Wagner wrote: > Thanks very much for writing this up, it’s very interesting. > > The one thing which I think needs improvement is the Copyable protocol. I > think that this is actually part of a larger problem in Swift, which is that > we

Re: [swift-evolution] [Manifesto] Ownership

Thanks very much for writing this up, it’s very interesting. The one thing which I think needs improvement is the Copyable protocol. I think that this is actually part of a larger problem in Swift, which is that we don’t expose enough information to generic code for it to operate safely. This

Re: [swift-evolution] [Manifesto] Ownership

> On Feb 25, 2017, at 11:41 AM, plx via swift-evolution > wrote: > 1: Collection Composition > > As much as the high-level picture is focused on safety, I’d just like to > request a strong focus on making sure the eventual ownership system addresses > the common

Re: [swift-evolution] [Manifesto] Ownership

1: Collection Composition As much as the high-level picture is focused on safety, I’d just like to request a strong focus on making sure the eventual ownership system addresses the common issues like avoiding copies when mutating through optionals, or when nesting collections, and so on.

Re: [swift-evolution] [Manifesto] Ownership

> Le 20 févr. 2017 à 23:16, John McCall a écrit : > > >> On Feb 20, 2017, at 4:55 PM, Florent Bruneau >> wrote: >> >> >>> Le 20 févr. 2017 à 18:22, John McCall a écrit : >>> On Feb 20, 2017, at 3:40 AM,

Re: [swift-evolution] [Manifesto] Ownership

> On Feb 20, 2017, at 4:55 PM, Florent Bruneau > wrote: > > >> Le 20 févr. 2017 à 18:22, John McCall a écrit : >> >>> >>> On Feb 20, 2017, at 3:40 AM, Florent Bruneau >>> wrote: >>> >>> Hi John, >>> >>>

Re: [swift-evolution] [Manifesto] Ownership

> Le 20 févr. 2017 à 18:22, John McCall a écrit : > >> >> On Feb 20, 2017, at 3:40 AM, Florent Bruneau >> wrote: >> >> Hi John, >> >> I've spent 3 hours reading the manifesto and its really very interesting. >> Despite the completeness of

Re: [swift-evolution] [Manifesto] Ownership

> On Feb 20, 2017, at 3:38 PM, John McCall wrote: > >> On Feb 20, 2017, at 4:26 PM, Matthew Johnson > > wrote: >>> On Feb 19, 2017, at 11:24 PM, John McCall >> > wrote:

Re: [swift-evolution] [Manifesto] Ownership

> On Feb 20, 2017, at 4:26 PM, Matthew Johnson wrote: >> On Feb 19, 2017, at 11:24 PM, John McCall > > wrote: >> >>> On Feb 18, 2017, at 11:08 AM, Matthew Johnson >>

Re: [swift-evolution] [Manifesto] Ownership

> On Feb 19, 2017, at 11:24 PM, John McCall wrote: > >> On Feb 18, 2017, at 11:08 AM, Matthew Johnson > > wrote: >> Hi John, >> >> This is fantastic! I’ve been eagerly anticipating this. It looks very much >> as I

Re: [swift-evolution] [Manifesto] Ownership

> On Feb 18, 2017, at 4:18 PM, Michel Fortin via swift-evolution > wrote: > Le 17 févr. 2017 à 3:25, John McCall via swift-evolution > a écrit : > >> func endScope(_ value: T) -> () {} > > Just to be sure, that is the same thing as `move`

Re: [swift-evolution] [Manifesto] Ownership

> On Feb 20, 2017, at 2:40 AM, Florent Bruneau via swift-evolution > wrote: > > Hi John, > > I've spent 3 hours reading the manifesto and its really very interesting. > Despite the completeness of the included discussion, I have a few > comments/concerns. > > >

Re: [swift-evolution] [Manifesto] Ownership

Hi John, I've spent 3 hours reading the manifesto and its really very interesting. Despite the completeness of the included discussion, I have a few comments/concerns. The first one is about the use a Copyable protocol whose conformance must be explicit in the module of the definition of the

Re: [swift-evolution] [Manifesto] Ownership

Le 17 févr. 2017 à 15:08, John McCall via swift-evolution a écrit : > > We don't have an initial implementation yet, sorry. I'm sure it'll vary a > lot by the application. My hope is that it'll just be a few extra non-atomic > loads and stores around every access,

Re: [swift-evolution] [Manifesto] Ownership

Le 17 févr. 2017 à 3:25, John McCall via swift-evolution a écrit : > func endScope(_ value: T) -> () {} Just to be sure, that is the same thing as `move` where you to discard the return value, right? let something = make() endScope(something) vs.

Re: [swift-evolution] [Manifesto] Ownership

Hi John, This is fantastic! I’ve been eagerly anticipating this. It looks very much as I was hoping it would. I can’t wait to see this vision come to life! You only show a mutating generator example. Do you also plan to allow shared generators? One topic you don’t touch on that feels

Re: [swift-evolution] [Manifesto] Ownership

> On Feb 17, 2017, at 2:51 PM, Xiaodi Wu wrote: > What a read! Two questions off the bat: > > 1. Any preliminary estimates as to what the performance cost of dynamic > enforcement is shaping up to be, at least in an initial implementation? It'd > have a direct impact on

Re: [swift-evolution] [Manifesto] Ownership

What a read! Two questions off the bat: 1. Any preliminary estimates as to what the performance cost of dynamic enforcement is shaping up to be, at least in an initial implementation? It'd have a direct impact on how "opt-in" the additional tools really are. 2. Without the intention of

Re: [swift-evolution] [Manifesto] Ownership

> On Feb 17, 2017, at 12:08 PM, John McCall wrote: >> On Feb 17, 2017, at 4:50 AM, Adrian Zubarev > > wrote: >> Hi John, would you mind creating a markdown document for this manifesto in >>

Re: [swift-evolution] [Manifesto] Ownership

> On Feb 17, 2017, at 4:50 AM, Adrian Zubarev > wrote: > Hi John, would you mind creating a markdown document for this manifesto in > https://github.com/apple/swift/tree/master/docs > ? :) > > Yes, it should go

Re: [swift-evolution] [Manifesto] Ownership

Hi John, would you mind creating a markdown document for this manifesto in https://github.com/apple/swift/tree/master/docs? :)___ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution