Re: [swift-evolution] [Review] SE-0137: Avoiding Lock-In to Legacy Protocol Designs

2016-08-12 Thread Rod Brown via swift-evolution
> * What is your evaluation of the proposal? +1. Agree we should deprecate legacy features that we don’t intend to support, to make future transitions easier for users. > * Is the problem being addressed significant enough to warrant a change > to Swift? Yes. > * Does this

Re: [swift-evolution] [Review] SE-0137: Avoiding Lock-In to Legacy Protocol Designs

2016-08-10 Thread John McCall via swift-evolution
> On Aug 10, 2016, at 2:03 PM, John McCall via swift-evolution > wrote: > > Hello Swift community, > > The review of "SE-0137: Avoiding Lock-In to Legacy Protocol Designs" begins > now and runs through August 14. The proposal is available here: > > >

[swift-evolution] [Review] SE-0137: Avoiding Lock-In to Legacy Protocol Designs

2016-08-10 Thread John McCall via swift-evolution
Hello Swift community, The review of "SE-0137: Avoiding Lock-In to Legacy Protocol Designs" begins now and runs through August 14. The proposal is available here: https://github.com/apple/swift-evolution/blob/master/proposals/0137-avoiding-lock-in.md