[swift-dev] TWISt-shout Newsletter 2016-04-11

Here is your TWISt-shout newsletter for the week of 2016-04-04 to 2016-04-10 https://github.com/pepperdog/TWISt-shout/blob/master/2016/TWISt-shout-2016-04-11.md Enjoy! -Kenny ___ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mai

Re: [swift-dev] A type-checking performance case study

> On Apr 8, 2016, at 11:47 AM, John McCall via swift-dev > wrote: > > One very drastic solution to this problem would be to eliminate non-labelled > overloads. (A perhaps more-reasonable way to describe this is to say that > argument labels are a part of the name, and therefore two declarati

Re: [swift-dev] A type-checking performance case study

> On Apr 11, 2016, at 8:35 AM, Joe Groff wrote: >> On Apr 8, 2016, at 11:47 AM, John McCall via swift-dev >> wrote: >> >> One very drastic solution to this problem would be to eliminate non-labelled >> overloads. (A perhaps more-reasonable way to describe this is to say that >> argument labe

Re: [swift-dev] Help needed: SE-0035 design detail

> On Apr 10, 2016, at 12:46 PM, Daniel Duan via swift-dev > wrote: > > Hi all, > > I'm in the process of implementing SE-0035, which limits capturing inout > parameter to @noescape contexts. The proposal is clear on capture behavior for > the following: > > 1. closure literals > 2. nested fun

Re: [swift-dev] Help needed: SE-0035 design detail

Great! I'll check return statements in addition to ApplyExpr arguments. - Daniel Duan On Mon, Apr 11, 2016 at 8:44 AM -0700, "Joe Groff" wrote: > On Apr 10, 2016, at 12:46 PM, Daniel Duan via swift-dev wrote: > > Hi all, > > I'm in the process of implementing SE-0035, which limi

Re: [swift-dev] Why are we re-linking?

> On Apr 7, 2016, at 14:01, Chris Lattner wrote: > > >> On Apr 6, 2016, at 11:08 AM, Jordan Rose via swift-dev >> wrote: >> >> I imagine it's because your git hash has changed, which is used in the >> --version output for swiftc. I'm not sure how to avoid that cost entirely, >> but we coul

Re: [swift-dev] SR-122 / CollectionsMoveIndices.swift Prototype

on Sun Apr 10 2016, Austin Zheng wrote: > I'm really sorry for dropping the ball and disappearing off the list. I'd like > to help out if I can. I'll check out the current branch tomorrow and see what > the status of the work is, but let me know if everything is done > already/there's > somethi

Re: [swift-dev] Why are we re-linking?

On 4/11/16 14:22, Jordan Rose via swift-dev wrote: >> On Apr 7, 2016, at 14:01, Chris Lattner > > wrote: >> >>> On Apr 6, 2016, at 11:08 AM, Jordan Rose via swift-dev >>> mailto:swift-dev@swift.org>> wrote: >> >> Could we move the hash to be a text file stored next to the

Re: [swift-dev] SR-122 / CollectionsMoveIndices.swift Prototype

Excellent! I'll begin working on this today. Austin > On Apr 11, 2016, at 11:07 AM, Dave Abrahams wrote: > > > on Sun Apr 10 2016, Austin Zheng > wrote: > >> I'm really sorry for dropping the ball and disappearing off the list. I'd >> like >> to help out if

Re: [swift-dev] SR-122 / CollectionsMoveIndices.swift Prototype

Anything to attempt on strings? I see you are considering consolidating down to a single index type for those, etc. Of course you also imply a large string rework that may happen in the future. -Shawn On Mon, Apr 11, 2016 at 11:07 AM Dave Abrahams wrote: > > on Sun Apr 10 2016, Austin Zheng wr

Re: [swift-dev] SR-122 / CollectionsMoveIndices.swift Prototype

On Mon, Apr 11, 2016 at 11:07 AM, Dave Abrahams wrote: > > on Sun Apr 10 2016, Austin Zheng wrote: > >> I'm really sorry for dropping the ball and disappearing off the list. I'd >> like >> to help out if I can. I'll check out the current branch tomorrow and see what >> the status of the work is,

Re: [swift-dev] SR-122 / CollectionsMoveIndices.swift Prototype

on Mon Apr 11 2016, Shawn Erickson wrote: > Anything to attempt on strings? I see you are considering consolidating down > to > a single index type for those, etc. Of course you also imply a large string > rework that may happen in the future. Yes, Strings need the same treatment (though it ma

Re: [swift-dev] SR-122 / CollectionsMoveIndices.swift Prototype

on Mon Apr 11 2016, Dmitri Gribenko wrote: > On Mon, Apr 11, 2016 at 11:07 AM, Dave Abrahams wrote: >> >> on Sun Apr 10 2016, Austin Zheng wrote: >> >>> I'm really sorry for dropping the ball and disappearing off the list. I'd >>> like >>> to help out if I can. I'll check out the current bran

Re: [swift-dev] Help needed: SE-0035 design detail

> Joe Groff via swift-dev swift.org> writes: > > return local // returning forms a closure, so ref is escapable My plan was to check all return statements with FuncDecl as results, if any of them has inout captures, complain. But this diagnosis is too coarse. A function can capture from any le

Re: [swift-dev] Help needed: SE-0035 design detail

> On Apr 11, 2016, at 1:28 PM, Daniel Duan via swift-dev > wrote: > >> Joe Groff via swift-dev swift.org> writes: >> >> return local // returning forms a closure, so ref is escapable > > My plan was to check all return statements with FuncDecl as results, if > any of them has inout captures

[swift-dev] [Swift CI] Failure: Swift Package - OS X (master)

Bot: https://ci.swift.org/view/Packages/job/oss-swift-package-osx/ Failing Tests (1): (Link ) Swift :: compiler_crashers/28279-swift-archetypebuilder-potentialarchet

Re: [swift-dev] Help needed: SE-0035 design detail

Ah, closures do get the same treatment here. Good point. - Daniel Duan On Mon, Apr 11, 2016 at 1:39 PM -0700, "Joe Groff" wrote: > On Apr 11, 2016, at 1:28 PM, Daniel Duan via swift-dev wrote: > >> Joe Groff via swift-dev swift.org> writes: >> >> return local // returning form

Re: [swift-dev] SR-122 / CollectionsMoveIndices.swift Prototype

Hi Dmitri, Happy to help with either/both of tests and new collection indices. Just point me in your preferred direction! Thanks, Austin Sent from my iPhone > On Apr 11, 2016, at 11:43 AM, Dave Abrahams wrote: > > >> on Mon Apr 11 2016, Dmitri Gribenko wrote: >> >>> On Mon, Apr 11, 2016 a

Re: [swift-dev] SR-122 / CollectionsMoveIndices.swift Prototype

On Mon, Apr 11, 2016 at 11:42 AM Dave Abrahams wrote: > > on Mon Apr 11 2016, Shawn Erickson wrote: > > > Anything to attempt on strings? I see you are considering consolidating > down to > > a single index type for those, etc. Of course you also imply a large > string > > rework that may happen

Re: [swift-dev] A type-checking performance case study

> On Apr 11, 2016, at 8:40 AM, John McCall wrote: > >> On Apr 11, 2016, at 8:35 AM, Joe Groff wrote: >>> On Apr 8, 2016, at 11:47 AM, John McCall via swift-dev >>> wrote: >>> >>> One very drastic solution to this problem would be to eliminate >>> non-labelled overloads. (A perhaps more-rea

Re: [swift-dev] SR-122 / CollectionsMoveIndices.swift Prototype

on Mon Apr 11 2016, Shawn Erickson wrote: > On Mon, Apr 11, 2016 at 11:42 AM Dave Abrahams wrote: > > on Mon Apr 11 2016, Shawn Erickson wrote: > > > Anything to attempt on strings? I see you are considering consolidating > down to > > a single index type for those, etc. Of cou

Re: [swift-dev] swift (ABI) and Windows

On Thu, Apr 7, 2016 at 2:12 PM, Saleem Abdulrasool wrote: > On Wed, Apr 6, 2016 at 10:21 AM, Saleem Abdulrasool > wrote: > >> Hi, >> >> I was playing around with the idea of swift and Windows since there are >> some interesting differences between COFF/PE and (ELF and MachO). >> >> PE/COFF does

Re: [swift-dev] SR-122 / CollectionsMoveIndices.swift Prototype

On Mon, Apr 11, 2016 at 3:16 PM, Dave Abrahams wrote: > > on Mon Apr 11 2016, Shawn Erickson wrote: > >> On Mon, Apr 11, 2016 at 11:42 AM Dave Abrahams wrote: >> >> on Mon Apr 11 2016, Shawn Erickson wrote: >> >> > Anything to attempt on strings? I see you are considering consolidating

Re: [swift-dev] swift (ABI) and Windows

> On Apr 11, 2016, at 3:19 PM, Saleem Abdulrasool via swift-dev > wrote: > > On Thu, Apr 7, 2016 at 2:12 PM, Saleem Abdulrasool > wrote: > On Wed, Apr 6, 2016 at 10:21 AM, Saleem Abdulrasool > wrote: > Hi, > > I was playing around with the idea of swift and Windows since there are some >

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 15.10 (master) #4134

/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/swiftpm/Tests/PackageType/PackageNameTests.swift:12:8: error: no such module 'XCTest' import XCTest ^ Mishal, have you seen this one before? This looks unrelated to my change. David > On Apr 11, 2016, at 11:48

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 15.10 (master) #4134

Hi David, I had removed --foundation because we were preparing for SR-0055, next build should be blue. Thanks, Mishal Shah > On Apr 11, 2016, at 11:49 PM, David Farler wrote: > > /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-15_10/swiftpm/Tests/PackageType/PackageN