Re: [swift-corelibs-dev] Informal Chat Medium

> On 3 Aug 2017, at 10:33, Alex Blewitt <alb...@apple.com> wrote: > >> On 2 Aug 2017, at 20:34, David Hart via swift-corelibs-dev >> <swift-corelibs-dev@swift.org> wrote: >> >> Hello Corelibs dev, > > Hi David, welcome! > >> A few m

[swift-corelibs-dev] Informal Chat Medium

Hello Corelibs dev, A few months back, I wanted to start contributing more seriously to Swift Open Source. I ended up helping out on the Swift Package Manager project and had a very positive experience. It’s not easy to jump into a big project and it would not have been such a success for me

Re: [swift-corelibs-dev] [swift-dev] Swift Encoders on Linux

Hi Tony, Looking forward to all this on Linux! On the same topic, I looked at the Measurement Swift type and did a diff between the shims in the swift repo and the version in corelibs-foundation and saw quite a few differences. Is this something that can be improved or it is a consequence of

Re: [swift-corelibs-dev] [swift-evolution] [swift-users] WWDC Meetup

Thanks for everybody that took the time to fill the form! There were many more responses than I expected, so dinner becomes difficult to organise. But thanks to a hand from another community member, we should have a venue confirmed soon. We are currently shooting for Tuesday evening. More

Re: [swift-corelibs-dev] [swift-evolution] [swift-users] WWDC Meetup

Hi everybody, After receiving a private question, I'd like to clarify something: I’m hoping that anybody interested in the Swift Open Source project, contributor or not, WWDC ticket holder or not, should feel free to come! This is definitely not something I meant to be restricted in any way.

Re: [swift-corelibs-dev] [swift-evolution] [swift-users] WWDC Meetup

Of course, I wouldn’t want to exclude anybody by default! In that case, I’m proposing dinner somewhere. I’ve setup a Google Forms to help organise it: http://goo.gl/forms/Oq6dK9fPNSCAVfL72 > On 07 Jun 2016, at 08:43, Jacob Bandes-Storch via

[swift-corelibs-dev] WWDC Meetup

I imagine that during WWDC a non-negligible proportion of the Swift Open Source contributors will be in or around San-Francisco. I’d very much like to profit from that opportunity to meet-up, get to know each other, talk Swift over some beers! Is anybody interested? If yes, any ideas for

Re: [swift-corelibs-dev] Objective-C Foundation vs CoreLibs Foundation

(about half way through I think). > On 23 May 2016, at 17:59, Tony Parker via swift-corelibs-dev > <swift-corelibs-dev@swift.org> wrote: > > Hi David, > >> On May 22, 2016, at 8:15 AM, David Hart via swift-corelibs-dev >> <swift-corelibs-dev@swift.org> wro

[swift-corelibs-dev] Objective-C Foundation vs CoreLibs Foundation

Hello, The discussion we had previously on this mailing list made it quite clear that: - Objective-C Foundation is the framework that is supposed to be used on all Darwin platforms, - swift-corelibs-foundation will be the Foundation framework for all other platforms, - Both frameworks will

[swift-corelibs-dev] Compilation Error - Which Toolchain

Hi people, Found some time to continue contributing to corelibs, but I’m getting a compilation error with master: NSGeometry.swift (line 39): 35 private var hash: Int { 36 #if arch(i386) || arch(arm) 37 return Int(Float(self.native).bitPattern) 38 #else 39 return

Re: [swift-corelibs-dev] Looking at corelibs-foundation

> On 14 May 2016, at 01:39, Tony Parker wrote: > > No. Only on Linux or other non-Darwin platforms. Ok, I understand that corelibs won't be the official "Foundation" framework on Darwin, but it will still be available under SwiftFoundation without having to compile

Re: [swift-corelibs-dev] Looking at corelibs-foundation

Thanks for all the answers :) These questions are dear to my heart because I plan on using corelibs-foundation on Darwin as soon as possible to share code between our iOS apps and web services. > On 14 May 2016, at 01:39, Tony Parker wrote: > > Over time it’s not

Re: [swift-corelibs-dev] Looking at corelibs-foundation

names of the module so its the >> same on all platforms? Isn’t it bad if portable code was doomed to have #if >> os() for all Foundation imports? If we do rename it, do we rename it to >> SwiftFoundation on Linux or do we rename it to Foundation on OS X (which >> would require

Re: [swift-corelibs-dev] Looking at corelibs-foundation

> On 13 May 2016, at 21:50, Tony Parker wrote: > > Technically, swift-corelibs-foundation is only part of the distribution on > Linux. On Darwin platforms, we use a combination of the overlay > (stdlib/public/SDK/Foundation directory in the Swift project) and the >

[swift-corelibs-dev] Looking at corelibs-foundation

Hello people, I wanted to start giving a hand on corelibs-foundation but hit two obstacles I’d like to discuss: It feels difficult to know where help is needed because the ReleaseNotes, Status and Know Issues docs have not been updated in a very long time, as if abandoned. Hopefully we can

Re: [swift-corelibs-dev] KVC dependent classes

ime present (so much of it relies on that dynamic behavior). > > - Tony > >> On Mar 14, 2016, at 4:14 PM, David Hart via swift-corelibs-dev >> <swift-corelibs-dev@swift.org> wrote: >> >> I was looking through Foundation for stuff to do and saw NSProgress, &

[swift-corelibs-dev] KVC dependent classes

I was looking through Foundation for stuff to do and saw NSProgress, NSExpression and NSSortDescriptor. They seem to be most reliant on KVC, and as KVC is not available without the Objective-C runtime, I’m not sure what those classes are doing here. Are those classes doomed to be dropped? Or is