[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 = DispatchQueue.Global

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 Software Group United Kingdom Phone: +44-1962-817078 IBM SDKs f

[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 `Cu

[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? instead

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 a

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-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 *could* just assume t

[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 y'a

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

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

Attached below is an updated version of the proposal. Again a rendered version is located at: https://gottesmm.github.io/proposals/high-level-arc-memory-operations.html Michael # Summary This document proposes: 1. adding the following ownership qualifiers to `load`: `[take]`, `[copy]`,

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, and

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

On Tue, Apr 26, 2016 at 8:49 AM, John McCall via swift-dev wrote: > > I think it's reasonable to assume that @_silgen_name is not being used for > objects that are external to the declaring module. That is, the > implementation model is that those declarations really are declaring a Swift > funct

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

> 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: > > https://gottesmm.github.io/proposals/high-level-arc-memory-operations.html >

[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 cle

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 may

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

Hi Enrico, Here is the doc for CI: https://github.com/apple/swift/blob/master/docs/ContinuousIntegration.md Thanks, Mishal Shah > On Oct 7, 2016, at 5:20 PM, Enrico Granata wrote: > > On that subject of trigger phrases, I think a while ago you sent out a way to > do cross-repository testing,

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: >> >> https://gottesmm.github.io/proposals/hig

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: > https://github.com/apple/swift/blob/master/docs/ContinuousInteg

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: >>> >>> Attached below is an updated version of the proposal. Again a

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 >> a scope, which is

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

> On Oct 7, 2016, at 9:25 PM, Andrew Trick wrote: > > >> On Oct 7, 2016, at 6:04 PM, Michael Gottesman via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >>> I wonder whether it might make more sense for load [borrow] to be a >>> different instruction. >>> There's a couple reasons for t

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 >>> mailto:swift-dev@swift.org>> wrote: >>> I wonder whether it might make

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 >> > wrote: >>> >>> On Oct 7, 2016, at 6:04 PM, Michael Gottesma

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 >> > 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: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 >> > wrote: >>> On Oct 7, 2016, at 9:25 PM, Andrew Tr

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

> On Oct 7, 2016, at 10:46 PM, Andrew Trick wrote: >> 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] swift (ABI) and Windows

> On Oct 7, 2016, at 4:08 PM, Paul Menage wrote: > On Tue, Apr 26, 2016 at 8:49 AM, John McCall via swift-dev > wrote: >> >> I think it's reasonable to assume that @_silgen_name is not being used for >> objects that are external to the declaring module. That is, the >> implementation model is t

[swift-dev] [discussion notes] SIL address types and borrowing

On swift-dev, John already sent out a great writeup on SIL SSA: Representing "address-only" values in SIL. While talking to John I also picked up a lot of insight into how address types relate to SIL ownership and borrow checking. I finally organized the information into these notes. This is not a