Re: [swift-dev] [semantic-arc][proposal] High Level ARC Memory Operations

> On Oct 7, 2016, at 10:36 PM, Michael Gottesman wrote: >> On Oct 7, 2016, at 10:26 PM, Andrew Trick > > wrote: >> >> >>> On Oct 7, 2016, at 10:08 PM, Michael Gottesman >> >

Re: [swift-dev] [semantic-arc][proposal] High Level ARC Memory Operations

> On Oct 7, 2016, at 10:36 PM, Michael Gottesman wrote: > >> >> On Oct 7, 2016, at 10:26 PM, Andrew Trick > > wrote: >> >> >>> On Oct 7, 2016, at 10:08 PM, Michael Gottesman >>

Re: [swift-dev] [semantic-arc][proposal] High Level ARC Memory Operations

> On Oct 7, 2016, at 10:26 PM, Andrew Trick wrote: > > >> On Oct 7, 2016, at 10:08 PM, Michael Gottesman > > wrote: >> >>> >>> On Oct 7, 2016, at 9:25 PM, Andrew Trick >> >

Re: [swift-dev] [semantic-arc][proposal] High Level ARC Memory Operations

> On Oct 7, 2016, at 10:08 PM, Michael Gottesman wrote: > >> >> On Oct 7, 2016, at 9:25 PM, Andrew Trick > > wrote: >> >> >>> On Oct 7, 2016, at 6:04 PM, Michael Gottesman via swift-dev >>>

Re: [swift-dev] [semantic-arc][proposal] High Level ARC Memory Operations

> On Oct 7, 2016, at 6:04 PM, Michael Gottesman via swift-dev > wrote: > >> I wonder whether it might make more sense for load [borrow] to be a >> different instruction. >> There's a couple reasons for that first. The first is that it's the only >> load which introduces

Re: [swift-dev] [semantic-arc][proposal] High Level ARC Memory Operations

> On Oct 7, 2016, at 6:04 PM, Michael Gottesman wrote: >> On Oct 7, 2016, at 5:09 PM, John McCall > > wrote: >>> On Oct 7, 2016, at 2:38 PM, Michael Gottesman >> > wrote:

Re: [swift-dev] @swift-ci now supports clean workspace for "smoke test" and "test and merge"

I added a section explaining what a smoke test is. Can you add a section describing what a clean smoke test is as well? > On Oct 7, 2016, at 5:24 PM, mishal_shah via swift-dev > wrote: > > Hi Enrico, > > Here is the doc for CI: >

Re: [swift-dev] [semantic-arc][proposal] High Level ARC Memory Operations

> On Oct 7, 2016, at 5:09 PM, John McCall wrote: > >> >> On Oct 7, 2016, at 2:38 PM, Michael Gottesman > > wrote: >> >> Attached below is an updated version of the proposal. Again a rendered >> version is located at: >>

Re: [swift-dev] @swift-ci now supports clean workspace for "smoke test" and "test and merge"

On that subject of trigger phrases, I think a while ago you sent out a way to do cross-repository testing, e.g. "test pull request 123 on apple/swift *together with* pull request 136 on apple/swift-lldb" If that is indeed possible, can I please ask for a refresher on how to achieve it? (and

[swift-dev] @swift-ci now supports clean workspace for "smoke test" and "test and merge"

@swift-ci now supports clean workspace for "smoke test" and "test and merge”, by using following trigger phrase. New: @swift-ci Please clean smoke test @swift-ci Please clean smoke test macOS @swift-ci Please clean smoke test Linux @swift-ci Please clean smoke test and merge @swift-ci Please

Re: [swift-dev] The Legend of the Toll-Free Swift -> ObjC Collection Bridge

on Fri Oct 07 2016, Alexis wrote: > I’ve been looking a lot into how Swift and Objective C collections > inter-convert because a bunch of necessary cleanup for ABI stability > interacts with it. Unfortunately I’ve run into some conflicting > information with respect to how stuff should work,

Re: [swift-lldb-dev] Cannot use swift REPL from stand alone lldb build

> On Oct 7, 2016, at 2:43 PM, Rex Fenley wrote: > > Thanks Enrico! Is there a download at swift.org that has > the patch available or do I have to manually apply it to the source? I believe you're going to have to manually apply the patch > And what

Re: [swift-lldb-dev] Cannot use swift REPL from stand alone lldb build

Thanks Enrico! Is there a download at swift.org that has the patch available or do I have to manually apply it to the source? And what about "SDK Path: error: unable to locate SDK No devices are available." errors when I simply try to run the lldb from the toolchain downloaded from swift.org? I

Re: [swift-dev] Reporting/Debugging Slow Swift Compile Time

Hello again! I wanted to follow up with some more numbers and feedback. I wasn't able to easily compile a single file from our project from the CLI. I started putting together a command with all of the necessary framework includes, flags, etc., but I moved on because it was taking awhile, becoming

[swift-dev] The Legend of the Toll-Free Swift -> ObjC Collection Bridge

I’ve been looking a lot into how Swift and Objective C collections inter-convert because a bunch of necessary cleanup for ABI stability interacts with it. Unfortunately I’ve run into some conflicting information with respect to how stuff should work, and how it seems to actually work. Hoping

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

On Wed, May 11, 2016 at 9:23 AM, Saleem Abdulrasool via swift-dev wrote: > > Unfortunately, ATM, the runtime is compacted into the stdlib, which has the > small problem of making the stdlib have references to the runtime functions > as if it were being dynamically linked. We

Re: [swift-dev] DispatchQueue function in Swift 3.0

I believe it got renamed to qos: DispatchQueue.global(qos: .userInteractive).async { } etc. > On Oct 7, 2016, at 6:11 AM, Yue Cui via swift-dev wrote: > > Does anyone know the equivalent function of DispatchQueue in Swift 3.0? > > Thanks in advance. >

Re: [swift-lldb-dev] Cannot use swift REPL from stand alone lldb build

This error usually comes from some Swift component in you app not being built with exactly the same Swift compiler as the one that the lldb you are using is built with. For instance, if you are building your own lldb, you have to use the Swift compiler that's built in the process of building

Re: [swift-dev] (Re-)compiling the stdlib

We were seeing some issues recently where the stdlib wouldn't get copied (actually lipo'd) into its final destination. Doug Coleman reverted the problem commit yesterday in https://github.com/apple/swift/pull/5166 . Can you update to the latest master

Re: [swift-corelibs-dev] Adding retain to CFCalendar.c - SR2879

Hi Alex, Thanks for digging into this. This seems like a correct solution for now. I think there is a larger question though, which is why it’s possible to overrelease kCFEmptyString. I think we skirted the issue early in bringup of SCL-Foundation, but constant strings are supposed to be

[swift-dev] KVO Context Param

Hey everyone, One of the things that came up in a code review today was the type of KVO's context param. If you look at the function signature it gets imported as UnsafeMutableRawPointer?. Is there ever a need to mutate this parameter, and if not can we change it to be UnsafeRawPointer?

[swift-dev] (Re-)compiling the stdlib

Hi there, quick question from someone who likes to get started on the stdlib and therefore sometimes likes to change an implementation, just to get a better understanding, what is going on. So let's say, I changed something in Bool.swift, e.g. to let the implementation of `description` in the

Re: [swift-dev] DispatchQueue function in Swift 3.0

Are you looking for the following? DispatchQoS.QoSClass. Regards C (Chris) Bailey Senior Technical Staff Member (STSM) Hursley Park Runtime Technologies for Java, Node.js and Swift Winchester, Hampshire SO21 2JN IBM

[swift-dev] DispatchQueue function in Swift 3.0

Does anyone know the equivalent function of DispatchQueue in Swift 3.0? Thanks in advance. For the DispatchQueue, the swift 3 has changed it's properties. The code for swift 2.xx looks like this: let priority =