[swift-dev] [Swift CI] Build Still Failing: OSS - Swift Package - OS X (swift 4.0) #263

2017-06-14 Thread no-reply--- via swift-dev
New issue found!Title: Report [FAILURE] oss-swift-4.0-package-osx [#263] Build URL:https://ci.swift.org/job/oss-swift-4.0-package-osx/263/ Project:oss-swift-4.0-package-osx Date of build:Wed, 14 Jun 2017 21:32:32 -0700 Build duration:1 hr 21 min Identified problems:Compil

[swift-dev] [Swift CI] Build Still Failing: OSS - Swift Package - OS X (master) #3522

2017-06-14 Thread no-reply--- via swift-dev
New issue found!Title: Report [FAILURE] oss-swift-package-osx [#3522] Build URL:https://ci.swift.org/job/oss-swift-package-osx/3522/ Project:oss-swift-package-osx Date of build:Wed, 14 Jun 2017 20:18:06 -0700 Build duration:1 hr 22 min Identified problems:Compile Error: T

[swift-dev] [Swift CI] Build Still Failing: OSS - Swift Package - OS X (swift 4.0) #262

2017-06-14 Thread no-reply--- via swift-dev
New issue found!Title: Report [FAILURE] oss-swift-4.0-package-osx [#262] Build URL:https://ci.swift.org/job/oss-swift-4.0-package-osx/262/ Project:oss-swift-4.0-package-osx Date of build:Wed, 14 Jun 2017 20:10:35 -0700 Build duration:1 hr 21 min Identified problems:Compil

[swift-dev] [Swift CI] Build Still Failing: OSS - Swift Package - OS X (swift 4.0) #261

2017-06-14 Thread no-reply--- via swift-dev
New issue found!Title: Report [FAILURE] oss-swift-4.0-package-osx [#261] Build URL:https://ci.swift.org/job/oss-swift-4.0-package-osx/261/ Project:oss-swift-4.0-package-osx Date of build:Wed, 14 Jun 2017 18:43:44 -0700 Build duration:1 hr 23 min Identified problems:Compil

[swift-dev] [Swift CI] Build Failure: OSS - Swift Package - OS X (master) #3521

2017-06-14 Thread no-reply--- via swift-dev
Title: Report [FAILURE] oss-swift-package-osx [#3521] Build URL:https://ci.swift.org/job/oss-swift-package-osx/3521/ Project:oss-swift-package-osx Date of build:Wed, 14 Jun 2017 17:43:22 -0700 Build duration:1 hr 23 min Identified problems:Compile Error: This build failed

[swift-dev] [Swift CI] Build Failure: OSS - Swift Package - OS X (swift 4.0) #260

2017-06-14 Thread no-reply--- via swift-dev
Title: Report [FAILURE] oss-swift-4.0-package-osx [#260] Build URL:https://ci.swift.org/job/oss-swift-4.0-package-osx/260/ Project:oss-swift-4.0-package-osx Date of build:Wed, 14 Jun 2017 17:33:37 -0700 Build duration:1 hr 9 min Identified problems:Compile Error: This bui

Re: [swift-dev] CI outage today

2017-06-14 Thread Mishal Shah via swift-dev
Upgrade completed! Thanks, Mishal Shah > On Jun 14, 2017, at 3:01 PM, Mishal Shah wrote: > > Hi, > > Starting the update process, I will send out another email once completed. > > Thanks, > Mishal Shah > >> On Jun 14, 2017, at 11:45 AM, Nicole Jacque via swift-dev >> mailto:swift-dev@swif

Re: [swift-dev] Swift question

2017-06-14 Thread Jordan Rose via swift-dev
[+swift-dev list] We use -verify mode to test warnings—you can see this a lot in tests with "expected-warning". The way to test for fix-its is to add "{{M-N=newtext}}" after the diagnostic text, where M and N are the start and end column numbers of the replacement (a half-open range). For an ins

Re: [swift-dev] statically initialized arrays

2017-06-14 Thread Michael Gottesman via swift-dev
> On Jun 14, 2017, at 11:24 AM, Erik Eckstein via swift-dev > wrote: > > Hi, > > I’m about implementing statically initialized arrays. It’s about allocating > storage for arrays in the data section rather than on the heap. > > Info: the array storage is a heap object. So in the following I’m

Re: [swift-dev] statically initialized arrays

2017-06-14 Thread Erik Eckstein via swift-dev
> On Jun 14, 2017, at 4:04 PM, Michael Gottesman wrote: > >> >> On Jun 14, 2017, at 11:24 AM, Erik Eckstein via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >> Hi, >> >> I’m about implementing statically initialized arrays. It’s about allocating >> storage for arrays in the data sect

Re: [swift-dev] statically initialized arrays

2017-06-14 Thread Erik Eckstein via swift-dev
> On Jun 14, 2017, at 12:03 PM, Jordan Rose wrote: > > > >> On Jun 14, 2017, at 11:24, Erik Eckstein via swift-dev > > wrote: >> >> Hi, >> >> I’m about implementing statically initialized arrays. It’s about allocating >> storage for arrays in the data section rat

Re: [swift-dev] CI outage today

2017-06-14 Thread Mishal Shah via swift-dev
Hi, Starting the update process, I will send out another email once completed. Thanks, Mishal Shah > On Jun 14, 2017, at 11:45 AM, Nicole Jacque via swift-dev > wrote: > > Hi All- > > This afternoon, we will be temporarily bringing down the CI, starting around > 3 PM, California time, in

Re: [swift-dev] statically initialized arrays

2017-06-14 Thread Dave Abrahams via swift-dev
on Wed Jun 14 2017, Erik Eckstein wrote: > Hi, > > I’m about implementing statically initialized arrays. It’s about > allocating storage for arrays in the data section rather than on the > heap. W00t! I'd like to do the same for String, i.e. encode the entire buffer in the data section. I was

Re: [swift-dev] statically initialized arrays

2017-06-14 Thread Jordan Rose via swift-dev
> On Jun 14, 2017, at 11:24, Erik Eckstein via swift-dev > wrote: > > Hi, > > I’m about implementing statically initialized arrays. It’s about allocating > storage for arrays in the data section rather than on the heap. > > Info: the array storage is a heap object. So in the following I’m u

[swift-dev] CI outage today

2017-06-14 Thread Nicole Jacque via swift-dev
Hi All- This afternoon, we will be temporarily bringing down the CI, starting around 3 PM, California time, in order to upgrade to the beta of Xcode 9 and the associated SDKs. We will also be briefly locking master while we land some source changes in support of the updated SDKs on both master

[swift-dev] statically initialized arrays

2017-06-14 Thread Erik Eckstein via swift-dev
Hi, I’m about implementing statically initialized arrays. It’s about allocating storage for arrays in the data section rather than on the heap. Info: the array storage is a heap object. So in the following I’m using the general term “object” but the optimization will (probably) only handle arra