New issue found!Title: Report
[FAILURE] oss-swift-4.1-package-osx [#155]
Build URL:https://ci.swift.org/job/oss-swift-4.1-package-osx/155/
Project:oss-swift-4.1-package-osx
Date of build:Sun, 12 Nov 2017 20:56:39 -0600
Build duration:1 hr 50 min
Identified
Problem with the bot throw I/O error while compiling one of the projects.
> On Nov 12, 2017, at 5:53 PM, no-re...@swift.org wrote:
>
> New issue found!
>
> [FAILURE] oss-swift-4.1-package-osx [#154]
>
> Build URL:https://ci.swift.org/job/oss-swift-4.1-package-osx/154/
>
New issue found!Title: Report
[FAILURE] oss-swift-4.1-package-osx [#154]
Build URL:https://ci.swift.org/job/oss-swift-4.1-package-osx/154/
Project:oss-swift-4.1-package-osx
Date of build:Sun, 12 Nov 2017 19:39:38 -0600
Build duration:13 min
Changes
> On Nov 12, 2017, at 5:37 PM, Mohammed Ennabah via swift-dev
> wrote:
>
> Hi All,
>
> I’m working on SR-3423, the issue basically is Swift does not allow using
> literals when they are represented as tuples. Now when I went through the
> codebase, I found that (AFAIK)
Hi All,
I’m working on SR-3423, the issue basically is Swift does not allow using
literals when they are represented as tuples. Now when I went through the
codebase, I found that (AFAIK) it can be fixed by either
a) giving tuples of literals a LiteralExpr, so there will be something like
On Nov 10, 2017, at 8:43 PM, Chris Lattner via swift-dev
wrote:
>> On Nov 4, 2017, at 9:52 PM, Erik Eckstein wrote:
Are compiler flags within the scope of the evolution process? -Osize has
no effect on source compatibility or any other
On Sun, Nov 12, 2017 at 1:37 PM, Tony Allevato
wrote:
>
>
> On Sat, Nov 11, 2017 at 1:53 PM Xiaodi Wu wrote:
>
>> On Sat, Nov 11, 2017 at 3:15 PM, Tony Allevato
>> wrote:
>>
>>>
>>>
>>> On Sat, Nov 11, 2017 at 10:28 AM
On Sat, Nov 11, 2017 at 1:53 PM Xiaodi Wu wrote:
> On Sat, Nov 11, 2017 at 3:15 PM, Tony Allevato
> wrote:
>
>>
>>
>> On Sat, Nov 11, 2017 at 10:28 AM Xiaodi Wu wrote:
>>
>>> On Sat, Nov 11, 2017 at 11:23 AM, Tony Allevato
On Sun, Nov 12, 2017 at 4:54 AM, Brent Royal-Gordon
wrote:
> On Nov 10, 2017, at 11:01 PM, Xiaodi Wu wrote:
>
> Nit: if you want to call it `ValueEnumerable`, then this should be
> `DefaultValueCollection`.
>
>
> I used `DefaultCaseCollection`
Hello all!
I'm looking for a body of work to do on the Swift compiler for an upcoming
programmer retreat I'm attending in January [1]. I've read a lot of blog
posts with tips for diagnosing slow Swift compile times [2], and I was
wondering if I could contribute to tooling in this area.
(Just to
> On Nov 10, 2017, at 11:01 PM, Xiaodi Wu wrote:
>
> Nit: if you want to call it `ValueEnumerable`, then this should be
> `DefaultValueCollection`.
I used `DefaultCaseCollection` because, although the protocol can work with any
type to return its values, this type can
11 matches
Mail list logo