[swift-evolution] Pitch: Replacement for FileHandle

Itai Ferber iferber at apple.com
Wed Feb 15 15:11:34 CST 2017

FYI, Tony is the manager of the Foundation team. :)
We care very much about making sure that the experience of using our 
framework is a positive one — the more Radars we get, the better we 
can prioritize improving APIs that are not working as well as they could 
be for our users. Even if the Radar gets duped to an existing one, thats 
one more +1 for that Radar saying "this is a problem".

I will search for your old Radar, but in any case, please do file a new 
one about this, and about any other issues you have, because we are 
indeed listening.

On 15 Feb 2017, at 10:41, Charles Srstka via swift-evolution wrote:

> > On Feb 15, 2017, at 10:52 AM, Tony Parker <anthony.parker at apple.com> 
> wrote:
>> Hi Charles,
>> Have you happened to file a radar for Foundation that I can look up 
>> (for both this and process)?
>> We are working hard on making sure that our API is right for Swift, 
>> and areas like this where we can make fairly trivial improvements are 
>> things that we can try to prioritize. As you say, the purpose of 
>> swift-corelibs-foundation is to present a unified API and prevent the 
>> need to fork. That means the best possible solution is to improve the 
>> API in Objective-C (where exceptions-as-control flow is wrong too) 
>> first, and then naturally flow that into Swift.
>> Thanks,
>> - Tony
> Honestly? I don’t remember. I feel like I would have sometime around 
> 2005 or 2006 or so, since that’s probably about when this first 
> started bothering me, but it’s been a decade, so my memory is hazy. 
> I do know that in the meantime, “considered harmful”-type articles 
> have been written about these classes, like this one from eight years 
> ago:
> https://mikeash.com/pyblog/friday-qa-2009-11-13-dangerous-cocoa-calls.html 
> <https://mikeash.com/pyblog/friday-qa-2009-11-13-dangerous-cocoa-calls.html>
> If you think it will actually prompt someone to change this, I’d be 
> happy to write up a new one, although I figure it would almost 
> certainly just get flagged as a duplicate.
> Charles

> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170215/e40318f3/attachment.html>

More information about the swift-evolution mailing list