[swift-dev] Implementing SE-0111: Remove type system significance of function argument labels

Hi all, I’ve been working on implementing SE-0111: Remove type system significance of function argument labels . Actually implementing this feature completely requires major surgery to

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #5527

I don't know? > On Jul 27, 2016, at 4:27 PM, Jordan Rose wrote: > > Error copying directory from > "/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/buildbot_incremental/swift-macosx-x86_64/lib/swift/appletvos" > to >

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

On Wed, Jul 27, 2016 at 3:58 PM Dave Abrahams wrote: > > on Wed Jul 27 2016, Ted Kremenek wrote: > > > - swift-evolution, swift-evolution-announce > > > > Dave/Max: can you speak this? > > >> On Jul 27, 2016, at 3:17 PM, Tony Allevato wrote: > >> > >>

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

on Wed Jul 27 2016, Ted Kremenek wrote: > - swift-evolution, swift-evolution-announce > > Dave/Max: can you speak this? >> On Jul 27, 2016, at 3:17 PM, Tony Allevato wrote: >> >> I noticed that while SE-0091 appears to be implemented (from a >> cursory glance at some of

Re: [swift-dev] [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-dev] End of source-breaking changes for Swift 3

> On Jul 27, 2016, at 1:21 PM, Jordan Rose via swift-dev > wrote: > >> SE-0107 - UnsafeRawPointer API >> Andy >> has been working on this. I still need to land one major

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

> On Jul 27, 2016, at 2:01 PM, Roman Levenstein wrote: > > > SE-0130 - Replace repeating Character and UnicodeScalar forms of String.init > > > This one was implemented

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

SE-0130 - Replace repeating Character and UnicodeScalar forms of String.init This one was implemented by me. It was committed yesterday. And, BTW, it was not mentioned in the original list of

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

> On Jul 27, 2016, at 12:38 PM, Ted Kremenek wrote: > > • SE-0045 - Add scan, prefix(while:), drop(while:), and iterate to the > stdlib The associated bug, SR-1516, is assigned to Russ Bishop, who said in late June that he had the non-lazy versions implemented. --

Re: [swift-dev] [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-dev] [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-dev] [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-dev] End of source-breaking changes for Swift 3

> On Jul 27, 2016, at 1:21 PM, Jordan Rose via swift-dev > wrote: > > Associating some proposals with their current implementers for the record… > >> On Jul 27, 2016, at 12:38, Ted Kremenek via swift-dev > > wrote: >> >>

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

> On Jul 27, 2016, at 1:21 PM, Jordan Rose via swift-dev > wrote: > > Associating some proposals with their current implementers for the record… > >> On Jul 27, 2016, at 12:38, Ted Kremenek via swift-dev > > wrote: >> >>

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

Associating some proposals with their current implementers for the record… > On Jul 27, 2016, at 12:38, Ted Kremenek via swift-dev > wrote: > > Dear friends, > > Today is July 27 — and the last planned day to take source-breaking changes > for Swift 3. It has been an

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

> On Jul 27, 2016, at 12:50 PM, Chris Lattner wrote: > > > >> On Jul 27, 2016, at 12:45 PM, Slava Pestov via swift-evolution >> > wrote: >> >> >>> On Jul 27, 2016, at 12:38 PM, Ted Kremenek via swift-dev >>>

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

> On Jul 27, 2016, at 12:45 PM, Slava Pestov via swift-evolution > wrote: > > >> On Jul 27, 2016, at 12:38 PM, Ted Kremenek via swift-dev >> > wrote: >> >> >> SE-0092 - Typealiases in protocols and protocol

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

Dear friends, Today is July 27 — and the last planned day to take source-breaking changes for Swift 3. It has been an incredible ride to this point, so let's take stock of where we are. Here are the list of currently accepted — but not yet (fully) implemented — evolution proposals (this is

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 15.10 (master) #1783

Adding Todd. > On Jul 27, 2016, at 11:25 AM, Mishal Shah via swift-dev > wrote: > > +Todd > > Hi Todd, > > Can you please look at this failure? Not sure, why its failing now. > > ERROR: [EXCEPTIONAL EXIT 11 (SIGSEGV)] test_indirect_enum_variables_gmodules >

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 15.10 (master) #1783

This fails periodically: [TestIndirectEnumVariables.py FAILED] It’s definitely not my commit, which passed linux CI multiple times. -Andy > On Jul 27, 2016, at 11:13 AM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-package-linux-ubuntu-15_10 [#1783] > > Build URL: >

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 15.10 (master) #1783

+Todd Hi Todd, Can you please look at this failure? Not sure, why its failing now. ERROR: [EXCEPTIONAL EXIT 11 (SIGSEGV)] test_indirect_enum_variables_gmodules (lang/swift/variables/indirect_enums/TestIndirectEnumVariables.py) Thanks! Mishal Shah > On Jul 27, 2016, at 11:22 AM, Andrew Trick

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #5519

Actually, what I reproduced is the other problem, which Michael already investigated > On Jul 27, 2016, at 10:23 AM, Andrew Trick wrote: > > FYI: Swift CI just passed on this commit minutes before this crash (it was > automerged). Of course validation tests also pass for me

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #5519

This was a CI infrastructure problem. Error copying a file. That’s why I directed to question to Mishal. The bot’s job coincided with locking the branch. -Andy > On Jul 27, 2016, at 10:23 AM, Andrew Trick via swift-dev > wrote: > > FYI: Swift CI just passed on this

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #5519

I just reproduced it locally. It's a swift compiler crash > On Jul 27, 2016, at 9:59 AM, Andrew Trick via swift-dev > wrote: > > Mishal, > > Can you tell me what happened here? > > -Andy > >> On Jul 27, 2016, at 9:57 AM, no-re...@swift.org

Re: [swift-dev] CI stabilization tomorrow

Hi, Master branch has been locked, I will update everyone once we unlock it. Thanks, Mishal Shah > On Jul 26, 2016, at 6:06 PM, Nicole Jacque via swift-dev > wrote: > > Hello All- > > Currently we are seeing a number of failures in CI on master. In order to > help