So after updating my sources, build-script fails to work with the following
error:
./utils/build-script: fatal error: can't find source directory for ninja (tried
/Volumes/data/wt/swift/master/ninja)
Why does it care about where my ninja source is? Why does "--build-ninja false"
not work?
Tha
I’d still like some feedback from the core team about whether value-type bound
protocols are worth formally proposing (and if so, what is the process like
these days). Thanks!
Dave
https://github.com/davezarzycki/swift/commit/32f32ce009f649772df57c94e2958bed4ef142ab
Or inline:
diff --git a/i
Even if we don't do coroutines as a user feature in Swift 5, we want to make
sure we implement coroutine-esque features (like materializeForSet) with an ABI
that we're satisfied with. Joe Groff and I were talking about the low-level
structure of that ABI, and I wanted to make sure that it was a
> On Sep 13, 2017, at 15:23, Matthew Johnson via swift-dev
> wrote:
>
>
>
> Sent from my iPhone
>
>> On Sep 13, 2017, at 11:56 AM, David Zarzycki via swift-dev
>> wrote:
>>
>>
>>
>>> On Sep 13, 2017, at 13:53, David Sweeris wrote:
>>>
>>>
On Sep 13, 2017, at 09:54, David Zarzyc
> On Sep 12, 2017, at 11:29 PM, Alwyn Concessao wrote:
>
> Okay.I see a couple of Swift files and .gyb files inside test/stdlib.I've
> made changes to the RangeReplaceableCollection protocol of the Swift
> stdlib.How can I write unit tests for that?Can I generate an Xcode project
> for the un
> On Sep 13, 2017, at 12:23 PM, Matthew Johnson via swift-dev
> wrote:
>
>
>
> Sent from my iPhone
>
>> On Sep 13, 2017, at 11:56 AM, David Zarzycki via swift-dev
>> wrote:
>>
>>
>>
>>> On Sep 13, 2017, at 13:53, David Sweeris wrote:
>>>
>>>
On Sep 13, 2017, at 09:54, David Zarz
Sent from my iPhone
> On Sep 13, 2017, at 11:56 AM, David Zarzycki via swift-dev
> wrote:
>
>
>
>> On Sep 13, 2017, at 13:53, David Sweeris wrote:
>>
>>
>>> On Sep 13, 2017, at 09:54, David Zarzycki via swift-dev
>>> wrote:
>>>
>>> Hello,
>>>
>>> As a part of a research project that
> On Sep 13, 2017, at 13:53, David Sweeris wrote:
>
>
>> On Sep 13, 2017, at 09:54, David Zarzycki via swift-dev
>> wrote:
>>
>> Hello,
>>
>> As a part of a research project that I’m working on, I’ve started bumping
>> into the need for value-type bound protocols (as opposed to the existi
> On Sep 13, 2017, at 09:54, David Zarzycki via swift-dev
> wrote:
>
> Hello,
>
> As a part of a research project that I’m working on, I’ve started bumping
> into the need for value-type bound protocols (as opposed to the existing
> class bound protocols). Is this something that would be wor
Looks like it crashed during shutdown. I’ll try to get a stack trace if it
crashes again via https://github.com/apple/swift/pull/11896.
> On Sep 13, 2017, at 12:59 AM, no-re...@swift.org wrote:
>
> [FAILURE] oss-swift-incremental-RA-linux-ubuntu-16_04 [#502]
>
> Build URL:
> https://ci.sw
Hello,
As a part of a research project that I’m working on, I’ve started bumping into
the need for value-type bound protocols (as opposed to the existing class bound
protocols). Is this something that would be worth proposing formally? Or should
I just keep the patch I have on my research branc
Looks like updating the module format number did not cause a rebuild of
TestFoundation. Can you clean the workspace?
> On Sep 13, 2017, at 9:30 AM, Ben Langmuir wrote:
>
> Thanks Arnold; if that doesn't do it I'll clean the workspace.
>
>> On Sep 13, 2017, at 8:57 AM, Arnold Schwaighofer >
Thanks Arnold; if that doesn't do it I'll clean the workspace.
> On Sep 13, 2017, at 8:57 AM, Arnold Schwaighofer
> wrote:
>
> It looks like TestFoundation was not rebuild. The failing test has passed on
> incremental linux bots who rebuild TestFoundation. If the executable still
> references
It looks like TestFoundation was not rebuild. The failing test has passed on
incremental linux bots who rebuild TestFoundation. If the executable still
references the removed array value witnesses I would not be surprised that it
would fail.
I suspect a clean build will make this test succeed. I
14 matches
Mail list logo