<div dir="ltr">Speaking of JIRA tasks, I remembered this morning that the versions of swift-corelibs-foundation and swift-corelibs-xctest expose public API that does not exist in their Apple counterparts. This is because of a bug in the linker that prevents us from marking attributes as private:<br><br>- <a href="https://bugs.swift.org/browse/SR-1129">https://bugs.swift.org/browse/SR-1129</a><br>- <a href="https://bugs.swift.org/browse/SR-1901">https://bugs.swift.org/browse/SR-1901</a><br><br>It would be great if we could fix this problem prior to the Swift 3 release, but if not, we need to be aware that some people may end up using or relying upon these "unintentionally public" API.<div><br></div><div>- Brian Gesiak<div><div><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 3, 2016 at 2:10 PM, Daniel Dunbar via swift-corelibs-dev <span dir="ltr"><<a href="mailto:swift-corelibs-dev@swift.org" target="_blank">swift-corelibs-dev@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Can someone file a bug to track how we are going to resolve this issue, and outline our options? I want to make sure we have enough eyes on it to make sure we get what we need for Swift 3.<div><br></div><div> - Daniel</div><div><div class="h5"><div><br><div><blockquote type="cite"><div>On Aug 1, 2016, at 3:08 AM, Chris Bailey <<a href="mailto:BAILEYC@uk.ibm.com" target="_blank">BAILEYC@uk.ibm.com</a>> wrote:</div><br><div><font size="2" face="sans-serif">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.</font>
<br>
<br><font size="2" face="sans-serif">Chris<br>
</font>
<br>
<br>
<br>
<br><font size="1" color="#5f5f5f" face="sans-serif">From:
</font><font size="1" face="sans-serif">David P Grove via swift-corelibs-dev
<<a href="mailto:swift-corelibs-dev@swift.org" target="_blank">swift-corelibs-dev@swift.org</a>></font>
<br><font size="1" color="#5f5f5f" face="sans-serif">To:
</font><font size="1" face="sans-serif">Swift corelibs dev
<<a href="mailto:swift-corelibs-dev@swift.org" target="_blank">swift-corelibs-dev@swift.org</a>></font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Date:
</font><font size="1" face="sans-serif">28/07/2016 18:50</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Subject:
</font><font size="1" face="sans-serif">Re: [swift-corelibs-dev]
Wrapping up Swift 3 for swift-corelibs</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Sent by:
</font><font size="1" face="sans-serif"><a href="mailto:swift-corelibs-dev-bounces@swift.org" target="_blank">swift-corelibs-dev-bounces@swift.org</a></font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size="3">Tony Parker wrote on 07/28/2016 01:41:55 PM:<br>
> <br>
> 1. Integrate swift-corelibs-dispatch into Foundation.</font></tt><font size="3"><br>
</font><tt><font size="3"><br>
Hi Tony,</font></tt><font size="3"><br>
</font><tt><font size="3"><br>
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...</font></tt><font size="3"><br>
</font><tt><font size="3"><br>
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.</font></tt><font size="3"><br>
</font><tt><font size="3"><br>
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.</font></tt><font size="3"><br>
</font><tt><font size="3"><br>
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?</font></tt><font size="3"><br>
</font><tt><font size="3"><br>
--dave</font></tt><font size="3"><br>
</font><tt><font size="2">_______________________________________________<br>
swift-corelibs-dev mailing list<br>
<a href="mailto:swift-corelibs-dev@swift.org" target="_blank">swift-corelibs-dev@swift.org</a><br>
</font></tt><a href="https://lists.swift.org/mailman/listinfo/swift-corelibs-dev" target="_blank"><tt><font size="2">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev</font></tt></a><tt><font size="2"><br>
</font></tt>
<br>
<br></div></blockquote></div><br></div></div></div></div>
<br>_______________________________________________<br>
swift-corelibs-dev mailing list<br>
<a href="mailto:swift-corelibs-dev@swift.org">swift-corelibs-dev@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-corelibs-dev" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev</a><br>
<br></blockquote></div><br></div>