[swift-corelibs-dev] Wrapping up Swift 3 for swift-corelibs

Chris Bailey BAILEYC at uk.ibm.com
Mon Aug 1 05:08:46 CDT 2016

I had a quick conversation with Daniel Dunbar on this. Adding -Xcc 
-fblocks as a default option to Swift PM (on Linux). The wrinkle is the 
availability of the blocks runtime - it would either need to become a 
pre-req for Swift, or needs one to be built into the package.


From:   David P Grove via swift-corelibs-dev 
<swift-corelibs-dev at swift.org>
To:     Swift corelibs dev <swift-corelibs-dev at swift.org>
Date:   28/07/2016 18:50
Subject:        Re: [swift-corelibs-dev] Wrapping up Swift 3 for 
Sent by:        swift-corelibs-dev-bounces at swift.org

Tony Parker wrote on 07/28/2016 01:41:55 PM:
> 1. Integrate swift-corelibs-dispatch into Foundation.

Hi Tony,

Hopefully this is on the task list already, but if it isn't we should add 
it before it gets to be too late to change the compiler...

When compiling a Swift program on Linux that imports Dispatch (or 
Foundation once the integration is done), the user has to give the extra 
compilation flags -Xcc -fblocks to enable block support.

We really need to land a change somewhere so that either (1) blocks 
support is always on for Linux or (2) importing Dispatch or Foundation 
automatically turns on blocks support.

I have some time today and tomorrow that I could use to work on this if no 
one is handling it already, but I'm not sure how best to tackle the 
problem.  Suggestions?

swift-corelibs-dev mailing list
swift-corelibs-dev at swift.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-corelibs-dev/attachments/20160801/530bdf6b/attachment.html>

More information about the swift-corelibs-dev mailing list