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

2016-04-22 Thread David Farler via swift-dev
This just finished compiling on the pull request bot ... Taking a look. David > On Apr 22, 2016, at 11:45 PM, no-re...@swift.org > wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-15_10 [#4446] > > Build URL: > https://ci.swift.org/job/oss-swift-incre

Re: [swift-dev] [Swift CI] Build Still Failing: OSS - Swift Package - Ubuntu 14.04 (master) #1095

2016-04-22 Thread Enrico Granata via swift-dev
REPL tests failing due to: before (last 100 chars): mplicitModuleImportKind): Assertion `M && "unable to auto-import module"' failed. yet another stale build problem? > On Apr 22, 2016, at 6:17 PM, no-re...@swift.org wrote: > > New issue found! > > [FAILURE] oss-swift-package-linux-ubuntu-14_0

Re: [swift-dev] RFC: "Near-miss" checking for defaulted protocol requirements

2016-04-22 Thread John McCall via swift-dev
> On Apr 22, 2016, at 3:33 PM, Douglas Gregor via swift-dev > wrote: > Hi all, > > A common complaint with protocol conformance checking is that it’s easy to > make a little mistake when trying to implement a protocol requirement that > has a default implementation. Here is a silly example: >

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

2016-04-22 Thread Greg Parker via swift-dev
> On Apr 22, 2016, at 4:13 PM, Greg Parker wrote: > > >> On Apr 22, 2016, at 3:14 PM, no-re...@swift.org wrote: >> >> [FAILURE] oss-swift-incremental-RA-osx [#3573] >> >> Build URL: https://ci.swift.org/job/oss-swift-incremental-RA-osx/3573/ >> Project: oss-swift-incremental-RA-osx >> D

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

2016-04-22 Thread Greg Parker via swift-dev
> On Apr 22, 2016, at 3:14 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-osx [#3573] > > Build URL:https://ci.swift.org/job/oss-swift-incremental-RA-osx/3573/ > Project: oss-swift-incremental-RA-osx > Date of build:Fri, 22 Apr 2016 14:51:48 -0700 > Build d

[swift-dev] Help with SR-1052: Handling generic return values

2016-04-22 Thread Trent Nadeau via swift-dev
Could someone who knows the generics system better than I give me a pointer for my question in https://bugs.swift.org/browse/SR-1052 (support for @discardableResult attribute)? Question: I'm starting to look at Part 5 (having the compiler use the new attr). What I have so far appears to be workin

[swift-dev] RFC: "Near-miss" checking for defaulted protocol requirements

2016-04-22 Thread Douglas Gregor via swift-dev
Hi all,A common complaint with protocol conformance checking is that it’s easy to make a little mistake when trying to implement a protocol requirement that has a default implementation. Here is a silly example:protocol P {   func foo(value: Float)}extension P {  func foo(value: Float) { } // defau

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

2016-04-22 Thread Douglas Gregor via swift-dev
The next commit fixes this. > On Apr 22, 2016, at 3:14 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-osx [#3573] > > Build URL:https://ci.swift.org/job/oss-swift-incremental-RA-osx/3573/ > > Project: o

Re: [swift-dev] Libraries written in Objective-C in Swift 3

2016-04-22 Thread Philippe Hausler via swift-dev
> On Apr 22, 2016, at 2:03 PM, Mike Berg via swift-dev > wrote: > > Hi everyone, > > A question has come up on my project that nobody seems to have an answer for. > I was hoping someone here might know: > > On my project, we have a longstanding iOS application that has both objC and > swift

Re: [swift-dev] Libraries written in Objective-C in Swift 3

2016-04-22 Thread David Smith via swift-dev
Hi Mike, The Foundation shipping with OS X and iOS is still written in Objective-C. The Swift-Corelibs Foundation is for use on other platforms currently. David > On Apr 22, 2016, at 2:03 PM, Mike Berg via swift-dev > wrote: > > Hi everyone, > > A question has come up on my project

[swift-dev] Libraries written in Objective-C in Swift 3

2016-04-22 Thread Mike Berg via swift-dev
Hi everyone, A question has come up on my project that nobody seems to have an answer for. I was hoping someone here might know: On my project, we have a longstanding iOS application that has both objC and swift source files. As is the case for most old apps out there (a few years), we regularly

Re: [swift-dev] Including `FileCheck` in downloadable toolchains

2016-04-22 Thread Ted Kremenek via swift-dev
SGTM > On Apr 21, 2016, at 9:28 PM, Daniel Dunbar via swift-dev > wrote: > > Hi all, > > I would like to propose that we include `FileCheck` in the downloadable > toolchains. > > The downloadable toolchains are quite useful for people who are wanting to > work on Swift projects that use Fil

Re: [swift-dev] test-repl-glibc failure

2016-04-22 Thread Mishal Shah via swift-dev
Todd and I had a quick chat, he is going to XFail this test but I will not publish new toolchains till we re-enable this test. Thanks, Mishal Shah > On Apr 22, 2016, at 11:12 AM, John McCall via swift-dev > wrote: > >> On Apr 22, 2016, at 11:09 AM, William Dillon via swift-dev >> mailto:sw

Re: [swift-dev] test-repl-glibc failure

2016-04-22 Thread John McCall via swift-dev
> On Apr 22, 2016, at 11:09 AM, William Dillon via swift-dev > wrote: > For me an objection to xfailing this is that it really isn't an expected > fail. Linux is actually broken. And it's therefore expected to fail until we fix it. Ideally, whoever added this understands that it's their respo

Re: [swift-dev] test-repl-glibc failure

2016-04-22 Thread William Dillon via swift-dev
For me an objection to xfailing this is that it really isn't an expected fail. Linux is actually broken. > On Apr 22, 2016, at 10:46 AM, Daniel Dunbar via swift-dev > wrote: > > I saw that, my question is specifically how this is going to be resolved. We > shouldn't have failures on the bots

Re: [swift-dev] test-repl-glibc failure

2016-04-22 Thread Daniel Dunbar via swift-dev
I saw that, my question is specifically how this is going to be resolved. We shouldn't have failures on the bots with no short term plan. Are there objections to XFAILing this test until resolved? - Daniel > On Apr 21, 2016, at 10:36 PM, Greg Parker wrote: > > >> On Apr 21, 2016, at 9:20 PM

Re: [swift-dev] Swift port to Windows : Offering help!

2016-04-22 Thread Shawn Erickson via swift-dev
Trying to get back on PR1950 today.. fighting to get things building again after a recent update-checkout. -Shawn On Thu, Apr 21, 2016 at 7:18 PM Sangjin Han via swift-dev < swift-dev@swift.org> wrote: > Hi Joel, > > I list some URLs. > > Bug/Feature report in http://bugs.swift.org > ---

Re: [swift-dev] Swift port to Windows : Offering help!

2016-04-22 Thread Joel Van Eenwyk via swift-dev
Hi Han, Thanks for all the details and links! I'll pull these down today and give the Cygwin port a shot to start with. Please let me know when the MSVC port is in a good place to start hammering on it. As for the JIRA tickets, are you alright with me updating some of those to include more detail

Re: [swift-dev] Including `FileCheck` in downloadable toolchains

2016-04-22 Thread Ryan Lovelett via swift-dev
On Fri, Apr 22, 2016, at 12:28 AM, Daniel Dunbar via swift-dev wrote: > Hi all, > > I would like to propose that we include `FileCheck` in the downloadable > toolchains. > > The downloadable toolchains are quite useful for people who are wanting > to work on Swift projects that use FileCheck (llb