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

[Brian Gesiak]

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:

- https://bugs.swift.org/browse/SR-1129
- https://bugs.swift.org/browse/SR-1901

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.

- Brian Gesiak


On Wed, Aug 3, 2016 at 2:10 PM, Daniel Dunbar via swift-corelibs-dev <
swift-corelibs-dev at swift.org> wrote:

> 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.
>
>  - Daniel
>
> On Aug 1, 2016, at 3:08 AM, Chris Bailey <BAILEYC at uk.ibm.com> wrote:
>
> 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.
>
> Chris
>
>
>
>
> 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
> swift-corelibs
> 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?
>
> --dave
> _______________________________________________
> swift-corelibs-dev mailing list
> swift-corelibs-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
>
>
>
>
> _______________________________________________
> swift-corelibs-dev mailing list
> swift-corelibs-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-corelibs-dev/attachments/20160803/5695a1dc/attachment.html>