Re: [swift-evolution] End of source-breaking changes for Swift 3

Fantastic! Here is the PR: https://github.com/apple/swift-evolution/pull/476 Two notes: > I had to introduce a FunctionArrowPrecedence to capture the parsing of -> in expression contexts. It looks like an implementation detail, so I didn't add it. > I found it convenient to continue to model

Re: [swift-evolution] End of source-breaking changes for Swift 3

Hi Taras, There’s more than enough evidence in the whole programming world to justify the existence of the classical for loop, also in Swift! Not only in “old” languages, for instance, take a look in Go. Excellent implementation there of the for;; https://tour.golang.org/flowcontrol/1

Re: [swift-evolution] End of source-breaking changes for Swift 3

Hi Ross, > On 29.07.2016, at 00:21, Ross O'Brien wrote: > > > This would imply, that if a decision is made, which in a later and changed > context proves to be a bad one, would be irreversible? > Better turn half way than to err in continuing. > Or, one decides to

Re: [swift-evolution] End of source-breaking changes for Swift 3

The reason C-style for loops were removed were because most of the time they could be represented by Swift syntax. Have you taken a look at stride(from:to:by:)? Saagar Jha > On Jul 28, 2016, at 15:08, Ted F.A. van Gaalen via swift-evolution > wrote: > > Hi

Re: [swift-evolution] End of source-breaking changes for Swift 3

> > > This would imply, that if a decision is made, which in a later and changed > context proves to be a bad one, would be irreversible? > Better turn half way than to err in continuing. > Or, one decides to go diving, but arriving at the location, notice that > the water is full of sharks? Still

Re: [swift-evolution] End of source-breaking changes for Swift 3

Hi Austin, please read inline. > On 28.07.2016, at 23:47, Austin Zheng wrote: > > > > On Thu, Jul 28, 2016 at 2:37 PM, Ted F.A. van Gaalen > wrote: > Hi Austin, thank you, please see inline > ? > I have explained

Re: [swift-evolution] End of source-breaking changes for Swift 3

Thanks, Chris. > On 28.07.2016, at 22:56, Chris Lattner wrote: > > >> On Jul 28, 2016, at 10:19 AM, Ted F.A. van Gaalen >> wrote: >>> The Swift team at Apple has reflected on this and decided what it "means" >>> for Swift 3 to be source compatible

Re: [swift-evolution] End of source-breaking changes for Swift 3

> On 28.07.2016, at 20:20, Karl Wagner wrote: > > +1. There have been lots of accepted proposals which I argued against, but > community-driven evolution means we have to compromise. This would imply, that if a decision is made, which in a later and changed context proves

Re: [swift-evolution] End of source-breaking changes for Swift 3

On Thu, Jul 28, 2016 at 2:37 PM, Ted F.A. van Gaalen wrote: > Hi Austin, thank you, please see inline > ? > I have explained this many times before, didn’t I? > > Its removal causes a very crucial limitation/change in the way > one writes programs, So writing about this

Re: [swift-evolution] End of source-breaking changes for Swift 3

Hi Austin, thank you, please see inline. > On 28.07.2016, at 19:33, Austin Zheng wrote: > > >> On Jul 28, 2016, at 10:19 AM, Ted F.A. van Gaalen via swift-evolution >> > wrote: >> >> -= Maybe it’s not

Re: [swift-evolution] End of source-breaking changes for Swift 3

> On Jul 28, 2016, at 4:15 AM, Anton Zhilin wrote: > > https://github.com/apple/swift/commit/c8c41b385c0312e562abe4952fa2d6794dec2e0f > > > Is SE-0077 going to be implemented for Swift 3?

Re: [swift-evolution] End of source-breaking changes for Swift 3

> Karl Wagner: In Plato's Crito, Socrates refuses to flee Athens after being > sentenced to death. He entered in to an agreement with the state to > participate in the process and respect its judgements, and reasons that to > violate the rules of the system because he believes the outcome

Re: [swift-evolution] End of source-breaking changes for Swift 3

+1. There have been lots of accepted proposals which I argued against, but community-driven evolution means we have to compromise. In Plato's Crito, Socrates refuses to flee Athens after being sentenced to death. He entered in to an agreement with the state to participate in the

Re: [swift-evolution] End of source-breaking changes for Swift 3

> On Jul 28, 2016, at 10:19 AM, Ted F.A. van Gaalen via swift-evolution > wrote: > > -= Maybe it’s not too late =- > For the moment the classical for ;; could simply > remain activated (Yes) in 3.0. because: I don't understand why you keep on

[swift-evolution] End of source-breaking changes for Swift 3

t; swift-evolution-annou...@swift.org > <mailto:swift-evolution-annou...@swift.org>, > swift-dev <swift-...@swift.org <mailto:swift-...@swift.org>> > Subject: [swift-evolution] End of source-breaking changes for Swift 3 > > Dear friends, > > Today is July

Re: [swift-evolution] End of source-breaking changes for Swift 3

> On Jul 28, 2016, at 8:30 AM, Brian Gesiak wrote: > Apologies if this was announced elsewhere: is commit access to master > restricted? It was, for about a day. It's less-restricted now, but there's a special process that doesn't have an exception for things like

Re: [swift-evolution] End of source-breaking changes for Swift 3

See the thread about stabilizing CI. The locked master while they worked out issues with the CI systems. Last I read it should be unlocked soon. On Thu, Jul 28, 2016 at 8:30 AM Brian Gesiak via swift-evolution < swift-evolution@swift.org> wrote: > Apologies if this was announced elsewhere: is

Re: [swift-evolution] End of source-breaking changes for Swift 3

Apologies if this was announced elsewhere: is commit access to master restricted? I noticed I couldn't merge some documentation improvements in https://github.com/apple/swift/pull/3815, and just wanted to make sure this was due to Swift 3 finalization. If commit access is restricted, is it safe

Re: [swift-evolution] End of source-breaking changes for Swift 3

https://github.com/apple/swift/commit/c8c41b385c0312e562abe4952fa2d6794dec2e0f Is SE-0077 going to be implemented for Swift 3? https://github.com/apple/swift/blob/master/stdlib/internal/SwiftExperimental/SwiftExperimental.swift Does this code actually run? If so, I will add "implemented" to the

Re: [swift-evolution] End of source-breaking changes for Swift 3

I noticed that while SE-0091 appears to be implemented (from a cursory glance at some of the affected types like Equatable and String), it looks like the named methods are still part of the FloatingPoint protocol and they still use global operators. Is anyone tracking the migration of that

Re: [swift-evolution] End of source-breaking changes for Swift 3

> On 27 Jul 2016, at 21:52, Jacob Bandes-Storch wrote: > > SE-0089 - Renaming String.init(_: T) > > > Has anyone worked on this? I have some time in the next couple of days and > might be

Re: [swift-evolution] End of source-breaking changes for Swift 3

> > >- SE-0089 - Renaming String.init(_: T) > > > > Has anyone worked on this? I have some time in the next couple of days and might be able to come up with an implementation in time.

Re: [swift-evolution] End of source-breaking changes for Swift 3

> SE-0104 - Protocol-oriented integers > We > used to have a prototype implementation of this, but it was removed (by > mistake?) by @moiseev a couple of weeks ago:

Re: [swift-evolution] End of source-breaking changes for Swift 3

> SE-0104 - Protocol-oriented integers > We > used to have a prototype implementation of this, but it was removed (by > mistake?) by @moiseev a couple of weeks ago: