Source-breaking proposals?


(Anton Zhilin) #1

Do I miss something, or proposals with source-breaking changes still can't
be submitted?
When will corresponsing guidelines be out? Are there any plans on that
matter?


(Karl) #2

I believe the situation is that we’re going to support Swift 3 syntax with a compiler flag, which frees us to make source-breaking changes for Swift 4.

AFAIK, how we support this in the compiler isn’t determined yet.

That’s what I take from Ted’s email: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160725/025587.html

- Karl

···

On 25 Sep 2016, at 18:38, Anton Zhilin via swift-evolution <swift-evolution@swift.org> wrote:

Do I miss something, or proposals with source-breaking changes still can't be submitted?
When will corresponsing guidelines be out? Are there any plans on that matter?
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution


(Dave Abrahams) #3

That's correct.

···

on Sun Sep 25 2016, Karl <swift-evolution@swift.org> wrote:

On 25 Sep 2016, at 18:38, Anton Zhilin via swift-evolution <swift-evolution@swift.org> wrote:

Do I miss something, or proposals with source-breaking changes still can't be submitted?
When will corresponsing guidelines be out? Are there any plans on that matter?
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

I believe the situation is that we’re going to support Swift 3 syntax with a compiler flag, which frees us to make source-breaking changes for Swift 4.

AFAIK, how we support this in the compiler isn’t determined yet.

That’s what I take from Ted’s email: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160725/025587.html

--
-Dave


(Chris Lattner) #4

Right. Also, it is worth saying that any source breaking change still has to have an ultra-compelling reason to be worth considering. Despite having a framework to support some source breaking changes, we still want to minimize them where ever possible.

-Chris

···

On Sep 26, 2016, at 11:07 AM, Dave Abrahams via swift-evolution <swift-evolution@swift.org> wrote:

on Sun Sep 25 2016, Karl <swift-evolution@swift.org> wrote:

On 25 Sep 2016, at 18:38, Anton Zhilin via swift-evolution <swift-evolution@swift.org> wrote:

Do I miss something, or proposals with source-breaking changes still can't be submitted?
When will corresponsing guidelines be out? Are there any plans on that matter?
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

I believe the situation is that we’re going to support Swift 3 syntax with a compiler flag, which frees us to make source-breaking changes for Swift 4.

AFAIK, how we support this in the compiler isn’t determined yet.

That’s what I take from Ted’s email: https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160725/025587.html

That's correct.