Re: [swift-corelibs-dev] Rules on adding dependencies

Hi Tom, I believe it’s important for us to keep our dependencies to an absolute minimum for the core libraries, since they will be distributed very widely. I would prefer to have our own implementation of the JSON parser in Foundation rather than use one from another project. The one from Darw

Re: [swift-corelibs-dev] Rules on adding dependencies

Good idea, I filed a bug for that here. https://bugs.swift.org/browse/SR-59 - Tony > On Dec 4, 2015, at 12:49 PM, Tom Leavy wrote: > > Hey Tony, > > That sounds like a good objective overall, thanks for clarifying. I think you > guys should write that so

Re: [swift-corelibs-dev] Will the Portability Stack include KVC/KVO support?

Hi Benoit, KVO and KVC rely heavily on the presence of the Objective-C runtime (for example, sometimes creating new subclasses for objects out of thin air). We’re not sure yet how or if we want to implement that functionality. In the meantime, filing a bug at bugs.swift.org would be a great wa

[swift-corelibs-dev] New contributions document

Hi everyone, Thank you so much for your interest in the Core Libraries over the first 2 days! Your response to the release has been overwhelming, and we’re really looking forward to working with you on this project going forward. I quickly realized that we needed to clarify some of the process

Re: [swift-corelibs-dev] Rules on adding dependencies

> On Dec 5, 2015, at 9:17 AM, Geordie Jay wrote: > > Sorry to spam, but I’ve just run some tests re: memory usage and found that > running NSJSONSerialization.JSONObjectWithData() repeatedly results in huge > memory usage (unbounded into the gigabytes). The pure Swift version I’ve been > work

Re: [swift-corelibs-dev] Rules on adding dependencies

Hi Geordie, The choice of NSData instead of String was very deliberate for NSJSONSerialization. The reason is that JSON is received from disk or the network as a data blob, not a String. Converting it into a String requires figuring out the encoding and doing a conversion. NSJSONSerialization l

Re: [swift-corelibs-dev] Proposal: add `noescape` attribute to public API (particularly libdispatch)

Pierre Habouzit for pointing this out) > > I provided a preliminary implementation at > https://github.com/apple/swift-corelibs-libdispatch/pull/6 > <https://github.com/apple/swift-corelibs-libdispatch/pull/6>, but it needs > refinement. Tony Parker mentioned commented

Re: [swift-corelibs-dev] Proposal: Conforming NSDate to Comparable

Hi Chris, Thanks for bringing this idea to the list. Is NSDate really the only thing that we want to conform to comparable, or is there a set of classes which should do so? I’d like to think about the larger set of consequences here (and if possible, deal with one coherent answer for all of Fo

Re: [swift-corelibs-dev] libdispatch roadmap and api addition proposal

Hi Joakim, > On Dec 7, 2015, at 4:55 AM, Joakim Hassila via swift-corelibs-dev > wrote: > > Hi, > > I think (and hope) that this is the proper forum for a few questions wrt to > libdispatch, otherwise any pointers are appreciated. > Yup, you’re in the right place. > We are currently using

Re: [swift-corelibs-dev] running Foundation tests

Hi Nathan, Check out the instructions here, and let us know if they don’t give you the info you need to get started: https://github.com/apple/swift-corelibs-foundation/blob/master/Docs/GettingStarted.md - Tony > On Dec 7, 2015, at 11:40 AM, Nathan Mann via swift-corelibs-dev > wrote: > > Lo

Re: [swift-corelibs-dev] [xctest] Who tests the tests?

it when building. Even if we change our minds later, there’s no doubt that having a starting point is valuable. - Tony > - Brian Gesiak > _ > From: Mike Ferris mailto:mfer...@apple.com>> > Sent: Friday, December 4, 2015 3:42 PM > Subject: Re: [s

Re: [swift-corelibs-dev] NSDate, NSDateFormatter

Hi Joe, Try this as a workaround: Set the LD_LIBRARY_PATH environment variable to $INSTALLED_LOCATION_OF_SWIFT/usr/lib/swift/linux This should only affect the REPL and not compiled code. I think this is supposed to be fixed in the top of tree Swift but not in the Dec 1 binary drop. - Tony >

Re: [swift-corelibs-dev] NSDate, NSDateFormatter

ib/swift/linux:$LD_LIBRARY_PATH > swift printdate.swift > <-- this is a blank line emitted by the first print(), which it should not be > --> > Dec 11, 2015, 6:52:33 PM > > Thanks for any insight and if I need to file a bug report I am happy to help, > Joe &g

Re: [swift-corelibs-dev] NSDecimal & NSDecimalNumber

Hi Dan, Florian, I agree with Philippe that NSDecimal is a particularly troublesome area in terms of how poorly the API is imported into Swift. Since NSDecimal is already a value type, it may be possible to do something better here ourselves without worrying about the bridging problem. It would

Re: [swift-corelibs-dev] libdispatch build issue

> On Dec 11, 2015, at 11:25 AM, Pierre Habouzit via swift-corelibs-dev > wrote: > >> On Dec 11, 2015, at 9:57 AM, Pierre Habouzit via swift-corelibs-dev >> mailto:swift-corelibs-dev@swift.org>> wrote: >> >>> >>> On Dec 11, 2015, at 9:02 AM, Philippe Hausler via swift-corelibs-dev >>> mailto

Re: [swift-corelibs-dev] NSDate Comparable & Equatable

ith a comment from Tony Parker about a discussion > currently going on about this. > > I seem to have missed out on this and currently not sure of the status on > this. > > Cheers > ___ > swift-corelibs-dev mailing l

Re: [swift-corelibs-dev] NSDecimal & NSDecimalNumber

ash. Let’s raise the issue on the more general swift-users list and see if anyone has any ideas. - Tony > >> On 11 Dec 2015, at 19:00, Tony Parker > <mailto:anthony.par...@apple.com>> wrote: >> >> Hi Dan, Florian, >> >> I agree with Philippe tha

Re: [swift-corelibs-dev] NSDate, NSDateFormatter

t functioning as expected. This > was against the latest main branch of the repositories and compiled on my > Ubuntu14.04 system. > > swift version 2.2-dev (LLVM 46be9ff861, Clang 4deb154edc, Swift 778f82939c) > Target: x86_64-unknown-linux-gnu > > Joe >

Re: [swift-corelibs-dev] [xctest] Removing outliers from performance tests

Hi Drew, Thanks for the detailed info on your issue. I see you filed a radar, and that is indeed the best way to make sure an issue on Darwin platforms is addressed. Unfortunately our corelibs implementation of XCTest isn’t ready yet for performance testing. - Tony > On Dec 10, 2015, at 3:41

Re: [swift-corelibs-dev] Unresolved enumeration symbols

Hi Joe, I see you used the preset for linux, but I just wanted to double-check that you are indeed building on Linux. - Tony > On Dec 12, 2015, at 3:48 PM, Joseph Bell via swift-corelibs-dev > wrote: > > Howdy. > > I'm using the basic build instructions (checking out swift, llvm, clang, >

Re: [swift-corelibs-dev] Unresolved enumeration symbols

6228.24 > TLB size: 1536 4K pages > clflush size: 64 > cache_alignment : 64 > address sizes : 48 bits physical, 48 bits virtual > power management: ts ttp tm 100mhzsteps hwpstate cpb > > > > On Sat, Dec 12, 2015 at 7:24 PM, Joe Bell <mailto:j...@iachiev

Re: [swift-corelibs-dev] Git history

Hi Tom, I’ve actually been thinking about this a lot over the past few days, but haven’t come to any real conclusion yet. The way I’ve traditionally worked on Foundation is that each commit has more content, and each commit is (almost) always associated with a bug. This is basically the proces

[swift-corelibs-dev] Starter bug: Run Foundation tests against OS X Foundation

Hi everyone, I filed a bug here that would be a great way for someone to jump into contributing to swift-corelibs-foundation: SR-276 The basic idea is that we could really use a way to run our Swift test suite against the system (OS X) Foundation. This wi

[swift-corelibs-dev] Upcoming holiday schedule

Hello fellow contributors, As you are aware, we are fast approaching the year-end holiday season. Here at Apple, many of us are taking some time off starting next week through the new year. As a result, it is likely that some pull requests will take more time than expected to review and merge.

Re: [swift-corelibs-dev] Upcoming holiday schedule

t; > - Brian Gesiak > > > > > > On Thu, Dec 17, 2015 at 9:03 AM -0800, "Tony Parker via swift-corelibs-dev" > mailto:swift-corelibs-dev@swift.org>> wrote: > > Hello fellow contributors, > > As you are aware, we are fast approaching the year-e

Re: [swift-corelibs-dev] Proposal: Make NSTask's standardInput/standardOutput/standardError properties type-safe

Hi Dan, Thank you for your proposal. This is the right place to start discussion of it. If we want to do this then we would have to make changes in both Darwin and open source versions, to maintain source compatibility. Out of curiosity, why propose an enum instead of an additional set of typed

Re: [swift-corelibs-dev] libdispatch epoll port

Hi Dzianis, > On Dec 17, 2015, at 12:36 PM, Dzianis Fedarenka via swift-corelibs-dev > wrote: > >>> On Dec 10, 2015, at 12:42 AM, Joakim Hassila via swift-corelibs-dev >>> wrote: >>> >>> Hi, >>> On 8 dec. 2015, at 16:56, Pierre Habouzit wrote: FWIW, this is my personal,

Re: [swift-corelibs-dev] Starter bug: Run Foundation tests against OS X Foundation

Awesome, thanks Ian! - Tony > On Dec 17, 2015, at 12:54 PM, Ian Ynda-Hummel wrote: > > Hey all, > > I'd like to claim this one. I'll assign to myself on Jira. > > On Thu, Dec 17, 2015 at 12:08 PM Tony Parker via swift-corelibs-dev > mailto:swift-corelibs-de

Re: [swift-corelibs-dev] NSThread properties

Hi Joe, Looks like an oversight. We should add them. - Tony > On Dec 17, 2015, at 6:45 PM, Joseph Bell via swift-corelibs-dev > wrote: > > Reading the Status page I see that NSThread is "fully implemented", yet. when > looking at the code and verifying by compiling, none of the properties: >

Re: [swift-corelibs-dev] NSXMLNode and Friends

Hi Robert, There actually already is some discussion on the swift-evolution list about a language feature to enable factory methods, which would help us to implement these kinds of things. It is a common pattern in Foundation to return subclasses from initializers (NSNull, NSPredicate are in th

Re: [swift-corelibs-dev] NSArray.descriptionWithLocale implementation

Hi Eugene, Interesting question. I think we may have to introduce a default implementation of -descriptionWithLocale:indent: which calls -descriptionWithLocale:, which has a default implementation of calling -description. It may be the case that we then have to limit the behavior to subclasses

Re: [swift-corelibs-dev] Inconsistencies between Foundation APIs

Hi Ian, Any place where the API differs should be marked with a comment like this: /// - Experiment: This is a draft API currently under consideration for official import into Foundation If not, then we found some place that we either need to change or propose a change for. We can track those

Re: [swift-corelibs-dev] [xctest] Terminology: What to call "swift-corelibs-xctest" and "Apple XCTest"

We’ve also used “Darwin Foundation” vs “Swift Core Libraries Foundation.” I’m open to suggestions on this from everyone. I haven’t found a set of terms that I’m really happy with yet. - Tony > On Dec 24, 2015, at 9:26 AM, Daniel Dunbar via swift-corelibs-dev > wrote: > > I believe we have be

Re: [swift-corelibs-dev] Equality, etc in Foundation

Hi Luke, Your proposed fix seems reasonable to me. Did you submit it as a PR too? Thanks, - Tony > On Dec 29, 2015, at 11:28 PM, Luke Howard via swift-corelibs-dev > wrote: > > Proposed fix: > > https://github.com/lhoward/swift-corelibs-foundation/commit/fe5dcce6ccf06d2f5b8e85c792012dbaee8f5

Re: [swift-corelibs-dev] Equality, etc in Foundation

Cool, thanks Philippe and Luke! - Tony > On Jan 4, 2016, at 12:59 PM, Philippe Hausler wrote: > > Actually I think we already got this one integrated. > >> On Jan 4, 2016, at 12:58 PM, Tony Parker via swift-corelibs-dev >> mailto:swift-corelibs-dev@swift.org

Re: [swift-corelibs-dev] #if __CORELIBS_FOUNDATION__

Hi Drew, This difference is a consequence of the lack of bridging between types like String and NSString. If this API returned [String : AnyObject], then the dictionary could not contain String (because String is not an object). This is something we will have to fix up in some comprehensive wa

Re: [swift-corelibs-dev] CChar vs Int8

Hi Luke, > On Jan 2, 2016, at 8:28 PM, Luke Howard via swift-corelibs-dev > wrote: > > Many Foundation APIs use Int8 instead of CChar when representing C strings, > e.g.: > var UTF8String: UnsafePointer >

Re: [swift-corelibs-dev] Inconsistencies between Foundation APIs

sewhere in the code. I'll work > under the assumption that inconsistencies are experimental and I'll open bugs > for things that are inconsistent but not marked as such. > > On Mon, Jan 4, 2016 at 2:51 PM Tony Parker <mailto:anthony.par...@apple.com>> wrote: > Hi

Re: [swift-corelibs-dev] LazySequenceType: make prefix return a lazy collection

Hi Mark, I’m going to loop in the swift-dev list for this question. - Tony > On Jan 4, 2016, at 5:15 AM, Mark Aron Szulyovszky via swift-corelibs-dev > wrote: > > Hi, > > I came across hit issue while chaining filter() and prefix() on lazy > sequences: > https://bugs.swift.org/browse/SR-461

Re: [swift-corelibs-dev] corelibs-xctest + swiftpm

Hi Keith, Also - the Xcode project is provided for development ease-of-use only. This version of XCTest is only for non-Darwin platforms, and that builds with the simple shell script that is in the root directory (build_script.py). - Tony > On Jan 4, 2016, at 9:19 AM, Daniel Dunbar via swift-c

Re: [swift-corelibs-dev] #if __CORELIBS_FOUNDATION__

Hi Drew, > On Jan 5, 2016, at 12:08 AM, Drew Crawford wrote: > > >> On Jan 4, 2016, at 3:09 PM, Tony Parker > <mailto:anthony.par...@apple.com>> wrote: >> >> In this particular case, how would you use the #if? Any should be source >> compatib

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

Hi David, It’s likely that we’ll have to come up with some alternative API in these cases. For example, in NSProgress I could imagine a callback for progress updates instead of observing the properties. It’s not ideal but I don’t think we want to undertake a reinvention of KVO when we do not ha

Re: [swift-corelibs-dev] Internal Tests

Using @testable makes sense to me. Let's try it out. - Tony > On Mar 15, 2016, at 7:54 AM, Robert Stephen Thompson via swift-corelibs-dev > wrote: > > If it doesn’t use it on Linux, it’s because I was mostly running tests in > Xcode heh, and didn’t end up needing it in the end. On Linux, of

Re: [swift-corelibs-dev] Cannot call CFStreamCreatePairWithSocket on Linux

Hi Pushkar, Yes, this is used by “getStreamsToHostWithName”. I think we’ll have to come up with a replacement implementation here, either by starting with the old CFNetwork open source code or writing our own. - Tony > On Mar 15, 2016, at 8:00 AM, Pushkar N Kulkarni via swift-corelibs-dev >

Re: [swift-corelibs-dev] Wrong type in NSHTTPURLResponse

Unfortunately the ObjC API doesn’t use generics for its dictionary: @property (readonly, copy) NSDictionary *allHeaderFields; So we need to get this fixed on Darwin Foundation first. I filed a bug to track this internally. - Tony > On Mar 15, 2016, at 10:42 AM, Daniel Eggert via swift-corelibs

Re: [swift-corelibs-dev] NSURLSession & libcurl

Awesome, thanks for taking this on! - Tony > On Mar 17, 2016, at 12:33 PM, Daniel Eggert via swift-corelibs-dev > wrote: > > I’ve made good progress on this. I’ll try to get something that’s merge-able > within the next week. It won’t be 100% complete by any means, but should > hopefully (A)

Re: [swift-corelibs-dev] NSOperationQueue and friends

Yah, we didn’t want to enable this by default yet because it’s still a work in progress. Also, it requires dispatch on Linux, which we are still working on getting integrated into the overall swift build process. - Tony > On Mar 30, 2016, at 4:42 AM, Daniel Eggert via swift-corelibs-dev > wro

Re: [swift-corelibs-dev] NSURL getResourceValue

Hi Zach, Daniel, > On Mar 31, 2016, at 11:03 AM, Zach Waldowski via swift-corelibs-dev > wrote: > > The semantics of the methods are fairly nuanced in ObjC. > > You can have a resource value that fails to be fetched, or one that > succeeded to fetch but had no value. A Swift version would mode

Re: [swift-corelibs-dev] [SE-0046] Implemented consistent function labels

These are turbulent times for syntax in Swift. :) Pretty soon now we're also going to have to deal with the swift renaming rules as applied to all functions in corelibs-foundation. - Tony > On Apr 8, 2016, at 3:12 AM, Daniel Eggert via swift-corelibs-dev > wrote: > > >>> On 08 Apr 2016, at

Re: [swift-corelibs-dev] [SE-0046] Implemented consistent function labels

-foundation up to date with the master of the Swift compiler. - Tony > On Apr 8, 2016, at 9:58 AM, Daniel Eggert wrote: > > On 08 Apr 2016, at 16:52, Tony Parker wrote: >> >> These are turbulent times for syntax in Swift. :) >> >> Pretty soon now we're als

Re: [swift-corelibs-dev] Migrate corelibs-foundation to the newest APIs

Hi Robert, This is something we really do need some help with. Our goal is to have the Linux version match the Darwin version exactly. There is also a PR up to change some of the results of the automatic renaming by the importer, here: https://github.com/apple/swift/pull/2093

Re: [swift-corelibs-dev] Migrate corelibs-foundation to the newest APIs

1 >> Date: Tue, 12 Apr 2016 09:57:38 -0700 >> From: Tony Parker > <mailto:anthony.par...@apple.com>> >> To: Robert F Dickerson > <mailto:rfdicker...@us.ibm.com>> >> Cc: swift-corelibs-dev@swift.org <mailto:swift-corelibs-dev@swift.org> >> Sub

Re: [swift-corelibs-dev] Crypto as part of the core libraries

Hi Travis, I think the best path for projects to become part of the corelibs “umbrella” is to start them off as community-driven, and once they have gained enough momentum we should consider folding them into the core distribution. This provides a lot of key benefits. Most importantly, the new

Re: [swift-corelibs-dev] Crypto as part of the core libraries

g Operations for Mobile and Distributed Systems > > From: mailto:anthony.par...@apple.com>> on behalf > of Tony Parker mailto:anthony.par...@apple.com>> > Date: Friday, April 15, 2016 at 9:02 AM > To: Travis Beech <mailto:tbe...@unwiredrevolution.com>>

Re: [swift-corelibs-dev] NSEnergyFormatter

We certainly appreciate help on this. Let us know if you have any questions. - Tony > On Apr 15, 2016, at 7:24 AM, Vojtěch Šťavík via swift-corelibs-dev > wrote: > > Hey guys, > > I'd like to help you with the project. I was looking for something simple to > start with and I'd choose NSEnerg

Re: [swift-corelibs-dev] NSURLSession & libcurl

I think that’s a fair approach - but does this even compile on Linux without dispatch in place? I get “no such module ‘Dispatch’” errors when compiling. - Tony > On Apr 18, 2016, at 11:24 AM, Pushkar N Kulkarni > wrote: > > Thanks for your great work on NSURLSession and friends, Daniel! > >

Re: [swift-corelibs-dev] NSTask and NSFileHandle implementation

Hi Alexander, Small incremental changes is usually a good approach. As for adding tests first, we can do that but we just need to make sure they don’t fail the build. What approach would you have in mind for that? - Tony > On Apr 22, 2016, at 1:37 AM, Alexander Alemayhu via swift-corelibs-dev

[swift-corelibs-dev] Merging swift-corelibs-foundation PRs

Hi everyone, I’m going through our open PRs for swift-corelibs-foundation and merging what I can. I’m sorry that some of them have been outstanding for so long - my time has been consumed with the value types work you recently saw on swift-evolution and a lot of other things. Most of these nee

Re: [swift-corelibs-dev] Use of pthread_main_np() in NSOperation

Since CF is really an implementation detail of Foundation for corelibs, let’s use the CF implementation for Foundation. - Tony > On May 10, 2016, at 12:10 PM, Chris Bailey via swift-corelibs-dev > wrote: > > NSOperation.swift currently makes a call to pthread_main_np() on line 536. > This ca

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

Hi David, > On May 11, 2016, at 4:02 PM, David Hart via swift-corelibs-dev > wrote: > > 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, > Statu

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

n covered elsewhere and can be picked up? > > James > > Sent from my iPhone > > On 13 May 2016, at 18:01, Tony Parker via swift-corelibs-dev > mailto:swift-corelibs-dev@swift.org>> wrote: > >> Hi David, >> >>> On May 11, 2016, at 4:02 PM, Da

Re: [swift-corelibs-dev] NSTask and try!

Hi James, > On May 13, 2016, at 12:25 PM, James Lee via swift-corelibs-dev > wrote: > > Following on from a previous discussion with Tests failing on OSX. I have > been looking into the failures. It seems that one of the earliest failures is > due to an error from a try! within NSTask.launch(

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

> On May 13, 2016, at 10:33 AM, Rob Allen wrote: > > Hi all, > >> On 13 May 2016, at 18:01, Tony Parker via swift-corelibs-dev >> mailto:swift-corelibs-dev@swift.org>> wrote: >> >> Hi David, >> >>> On May 11, 2016, at 4:02 PM, David H

Re: [swift-corelibs-dev] NSTask and try!

uld try to get something in place so we’re not failing on OS X in the short term for sure. - Tony > Sent from my iPhone > >> On 13 May 2016, at 20:48, Tony Parker wrote: >> >> Hi James, >> >>> On May 13, 2016, at 12:25 PM, James Lee via swift-corelibs-dev

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

corelibs-dev >> mailto:swift-corelibs-dev@swift.org>> wrote: >> >> >>> On 13 May 2016, at 21:50, Tony Parker >> <mailto:anthony.par...@apple.com>> wrote: >>> >>> Technically, swift-corelibs-foundation is only part of the distributio

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

module on Linux? Foundation? Foundation > If those are different, isn’t there an incentive for having the same moule > name on all platforms? > > David. > The system Foundation.framework on Darwin and swift-corelibs-foundation on Linux are both called “Foundation”. Hope tha

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

exactly the use case we want to enable. In fact... > >> On 14 May 2016, at 01:39, Tony Parker wrote: >> >> Over time it’s not clear how the two will evolve, but we want them to evolve >> together from an API point of view at least. > > I have a hard time seei

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

Yah, because of the integration with the CI system (which we absolutely want), master of scl-foundation should certainly track Swift master. I’m hoping that this kinds of incompatibilities are a temporary problem, and that as things settle down in the Swift 3 release we will have less source br

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

Hi David, > On May 22, 2016, at 8:15 AM, David Hart via swift-corelibs-dev > wrote: > > 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

Re: [swift-corelibs-dev] swift-corelibs-xctest JIRA dashboard

This is slick! I would love to have one for Foundation too (although my understanding of JIRA is limited at best). - Tony > On May 22, 2016, at 12:47 PM, Brian Gesiak via swift-corelibs-dev > wrote: > > Hello all! > > If you're like me, you might be curious how Core Libraries like > swift-

Re: [swift-corelibs-dev] [swift-users] String manipulation (replacingOccurrences) in Linux swift

Hi Brent, > On May 26, 2016, at 2:29 PM, Brent Royal-Gordon via swift-corelibs-dev > wrote: > >>#if os(Linux) >>print("Let's change those carriage returns...") >>processedString = string.replacingOccurrences(of: "\r\n", with: >> "\n") >>#else >>

[swift-corelibs-dev] Xcode 8 beta 1 and swift-corelibs-foundation

Hello everyone, If you’ve downloaded Xcode 8 beta 1, you’ve seen some of the great changes we’ve got coming up for Swift 3 on Darwin. We have been working in parallel on those improvements and the changes that we need to bring swift-corelibs-foundation up-to-date, including: * new value types

Re: [swift-corelibs-dev] Xcode 8 beta 1 and swift-corelibs-foundation

't be applying the same kinds > of grand renaming to XCTest -- would just like to confirm that point. > > - Brian Gesiak > >> On Tue, Jun 14, 2016 at 1:24 PM, Tony Parker via swift-corelibs-dev >> wrote: >> Hello everyone, >> >> If you’ve downloaded Xco

Re: [swift-corelibs-dev] Suggested DateInterval API improvement

Hi Dave, We had some extensive discussion about this ourselves, but we couldn’t come up with a compelling use case for a negative time interval. Can you describe how you wanted to use it? - Tony > On Jun 17, 2016, at 2:01 PM, Dave Lyon via swift-corelibs-dev > wrote: > > In attempting to us

Re: [swift-corelibs-dev] Suggested DateInterval API improvement

quivalent basis with normal forward date intervals. > A separate specific initializer for it might be useful, though. > > - Greg > >> On Jun 20, 2016, at 4:12 PM, Tony Parker via swift-corelibs-dev >> mailto:swift-corelibs-dev@swift.org>> wrote: >> >>

Re: [swift-corelibs-dev] Xcode 8 beta 1 and swift-corelibs-foundation

Hi everyone, We’ve merged the swift-3 branch into master. Please let us know if you encounter any issues. I’m going to keep going through pull requests, but some may be out of date and need rebasing now. Thanks, - Tony > On Jun 14, 2016, at 10:24 AM, Tony Parker wrote: > > Hello

Re: [swift-corelibs-dev] Xcode 8 beta 1 and swift-corelibs-foundation

I checked on this and you’re right that it returns a random UUID if decoding fails. This is a truly strange idea, so I’ve filed a bug for us to fix that there too (26930786). - Tony >> On 22 Jun 2016, at 2:46 AM, Tony Parker via swift-corelibs-dev >> mailto:swift-corelibs-dev@swift

Re: [swift-corelibs-dev] NSFileHandle implementation

Hi Rhett, Sure, we’d love some help here. One challenge with this particular API is that we haven’t yet integrated libdispatch into Foundation (work is in progress right now), so the async behavior might be difficult to implement. - Tony > On Jun 22, 2016, at 2:39 PM, Gwynne Raskind via swift

Re: [swift-corelibs-dev] NSStream implementation

Hi Mamatha, This seems like a reasonable starting point. Thanks for taking this on! - Tony > On Jun 23, 2016, at 1:14 AM, Mamatha Busi via swift-corelibs-dev > wrote: > > Hi > > Looking into the NSStream class in Foundation, the NSInputStream and > NSOutputStream subclasses have their APIs

Re: [swift-corelibs-dev] NSKeyValueCoding and the Swift Foundation

Hi Lars, Unfortunately, I don’t think there is anything planned for Swift 3 in this area. Beyond that we just don’t have any concrete information yet. This is a pretty big topic, so it’s likely we’ll need to have some extended design discussions about what reflection or runtime dynamism in gene

Re: [swift-corelibs-dev] Query on NSLog

Hi Sai, Out of curiosity, why NSLog instead of Swift’s print function? - Tony > On Jun 27, 2016, at 4:37 AM, Sai Kanduri via swift-corelibs-dev > wrote: > > Hi All, > > Currently NSLog has only one internal function NSLog() which can be used > only by Foundation classes.Can this be made

Re: [swift-corelibs-dev] Query on NSLog

ke it public. > >> On 6 Jul 2016, at 5:42 AM, Tony Parker via swift-corelibs-dev >> mailto:swift-corelibs-dev@swift.org>> wrote: >> >> Hi Sai, >> >> Out of curiosity, why NSLog instead of Swift’s print function? >> >> - Tony >> >>&g

Re: [swift-corelibs-dev] Internal Tests

erequisite for reliability - Edsger W. Dijkstra > > > > -swift-corelibs-dev-boun...@swift.org > <mailto:-swift-corelibs-dev-boun...@swift.org> wrote: - > To: Robert Stephen Thompson <mailto:robert.thomp...@willowtreeapps.com>> > From: Tony Parker via

Re: [swift-corelibs-dev] NSOperationQueue

Hi JNS, We do want OperationQueue and friends to be part of swift-corelibs-foundation. What’s held us back so far is the lack of libdispatch support on Linux. That’s still making progress, so I hope we can tackle this one pretty soon. - Tony > On Jul 10, 2016, at 10:01 AM, JNS via swift-coreli

Re: [swift-corelibs-dev] NSOrderedSet implementation

Hi Sowmya, I haven’t heard of anyone working on this yet, so if you would like to contribute an implementation that would be great! - Tony > On Jul 12, 2016, at 3:07 AM, Sowmya Vikram via swift-corelibs-dev > wrote: > > Hi pushkar > > I would like to implement NSOrderedSet and its related c

Re: [swift-corelibs-dev] small nit in NSKeyedArchiver.swift

This looks correct to me. Can you file JIRA or put up a PR? Thanks! - Tony > On Jul 19, 2016, at 11:16 PM, Luke Howard via swift-corelibs-dev > wrote: > > Posting to mailing list as I’m not able to test this right now, but I suspect > this patch should be applied – > > diff --git a/Foundatio

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

Hi everyone, We’re getting close to the finish line for Swift 3, but we still have some work to do in swift-corelibs, especially swift-corelibs-foundation. I want to lay out what our goals and plans are for the next few weeks. As Swift 3 has been wrapping up, an immense number of important synt

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

Hi Dan, I believe Matt is working on getting the remaining overlay changes into Linux as we speak. - Tony > On Jul 28, 2016, at 10:48 AM, Dan Stenmark > wrote: > >> 1. Integrate swift-corelibs-dispatch into Foundation. > > Are there any lingering items in swift-corelibs-dispatch that are st

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

Hi Dave, I don’t believe anyone is looking into this. If you want to do that, I think now would be the time! - Tony > On Jul 28, 2016, at 10:50 AM, David P Grove via swift-corelibs-dev > wrote: > > Tony Parker wrote on 07/28/2016 01:41:55 PM: > > > > 1. Integrate

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

t.org>> wrote: > The overlay changes were merged to corelibs libdispatch this morning. > > Sent from my iPhone. > > On Jul 28, 2016, at 2:03 PM, Tony Parker via swift-corelibs-dev > mailto:swift-corelibs-dev@swift.org>> wrote: > >> Hi Dave, >> >&g

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

Ferris) > Just to confirm, we are not resolving https://bugs.swift.org/browse/SR-710 > <https://bugs.swift.org/browse/SR-710>, "Generate XCTestCaseProvider entries > on Linux", in time for the Swift 3 release. Is this correct? > > - Brian Gesiak > > >

Re: [swift-corelibs-dev] IndexPath performance

Hi Stephan, Do you have some benchmarks that you could share? That would help us focus performance work in the right area. I know that 2-item IndexPaths are super common with UIKit collection view and friends, so we may just want to special case those. Unfortunately, NSIndexPath is not abstrac

Re: [swift-corelibs-dev] [SR-1608]

Hi David, Thanks for helping! Can you check out some of our current open PRs to make sure your work isn’t overlapping? We’ve had some contributions in this area recently that we still need to finish merging. - Tony > On Jul 29, 2016, at 11:28 PM, David Liu via swift-corelibs-dev > wrote: >

Re: [swift-corelibs-dev] IndexPath performance

be able to tie the current overlay code to a specific OS instead of having to run back several releases. Thanks, - Tony > > On 2 August 2016 at 11:09, Tony Parker <mailto:anthony.par...@apple.com>> wrote: > Hi Stephan, > > Do you have some benchmarks that you could

Re: [swift-corelibs-dev] Is NSXMLParser completely implemented (swift-3.0-PREVIEW-2)

Hi Tim, Can you file a JIRA for us? Swift doesn’t support optional methods in protocols, so for ObjC protocols that are optional on OS X I tried to provide default implementations that do nothing on Linux. It’s possible I missed some for NSXMLParser. - Tony > On Aug 2, 2016, at 8:08 PM, Tim K

Re: [swift-corelibs-dev] Query on Bundle.unload()

Hi Sai, What I understand from the Swift runtime team is that unloading of Swift executables is basically unsupported. There are a lot of challenges to getting unloading right in general, because it can remove things like “constant” strings and cause mysterious crashes. - Tony > On Aug 3, 201

Re: [swift-corelibs-dev] Query on init methods in Data.swift

Hi Simon, The correct one is the non-optional version. We changed it after some discussion about if it made sense for Data to attempt to return nil here, when there are so many ways for memory allocation to fail without returning an optional. We’re working on updating the swift-corelibs-founda

Re: [swift-corelibs-dev] [SR-1608]

before last weekend. I tried to build the > TC manually and TC failed as well. Any suggestions to rebase and build/test? > > Cheers > > Dave > > > On Tue, Aug 2, 2016 at 2:22 AM, Tony Parker <mailto:anthony.par...@apple.com>> wrote: > Hi David, > >

Re: [swift-corelibs-dev] Swiftier? implementation of Measurement and Unit in Foundation

Hi Joanna, An important requirement of the design of measurements and units was that it had to work in Objective-C as well, where protocols do not have as many capabilities as they do in Swift. The bridging into Swift can only do so much, and frankly it didn’t seem to be the case that tradition

Re: [swift-corelibs-dev] Building with Xcode

Hi Luke, In Xcode it should be possible to set the build order like this: Foundation XCTest TestFoundation which should resolve the ordering issue, right? I do this with a build scheme. - Tony > On Aug 17, 2016, at 6:13 PM, Luke Howard via swift-corelibs-dev > wrote: > > This is probably a

  1   2   >