Re: [swift-corelibs-dev] NSAttributedString attributesAtIndex return an optional.

> This may be better for the swift-evolution list, but I really do not like the > fact that subscripting is a "hard" error. I think the language should have as > little hard errors as possible to improve on how much the compiler can check > for you. I think the idea is that, if you’re subscript

Re: [swift-corelibs-dev] NSAttributedString attributesAtIndex return an optional.

This may be better for the swift-evolution list, but I really do not like the fact that subscripting is a "hard" error. I think the language should have as little hard errors as possible to improve on how much the compiler can check for you. It seems like a holdover from C to me. Having those be

[swift-corelibs-dev] Implicit conversions between types will be disabled in Foundation

After seeing numerous failures in type conversions that work in the Mac OS X Xcode project target but don’t work in the Linux target, we have come to the conclusion that implicit conversions are going to have to be disabled for now. I have a change incoming that will require all conversions such

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

> On Dec 8, 2015, at 9:05 AM, Daniel A. Steffen via swift-corelibs-dev > wrote: > >> >> On Dec 8, 2015, at 6:11, Joakim Hassila wrote: >> >> Hi Daniel, >> >> >>> On 7 dec. 2015, at 23:11, Daniel A. Steffen wrote: >>> >>> FWIW I’ve updated the macosforge svn repo trunk to match with github

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

-Pierre > On Dec 8, 2015, at 7:34 AM, Joakim Hassila via swift-corelibs-dev > wrote: > > Hi Pierre, > > Thanks for the good explanation, will try to respond inline below: > >> On 7 dec. 2015, at 23:10, Pierre Habouzit > > wrote: >> >> Hi Joakim, Kevin, >> >> [ F

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

> On Dec 8, 2015, at 6:11 AM, Joakim Hassila via swift-corelibs-dev > wrote: > > Hi Daniel, > > >> On 7 dec. 2015, at 23:11, Daniel A. Steffen wrote: >> >> FWIW I’ve updated the macosforge svn repo trunk to match with github >> swift-corelibs-libdispatch trunk (sans the PRs, excecpt for my

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

Hi Pierre, Thanks for the good explanation, will try to respond inline below: On 7 dec. 2015, at 23:10, Pierre Habouzit mailto:phabou...@apple.com>> wrote: Hi Joakim, Kevin, [ Full disclosure, I made that reply in rdar://problem/16436943 and your use case was slightly different IIRC but you’r

Re: [swift-corelibs-dev] NSAttributedString attributesAtIndex return an optional.

> Been playing around with NSAttributedString and cannot decide on the best way > to implement the (attributesAtIndex: effectiveRange) and other methods with > similar functionality. > > In the ObjC world I would expect an empty NSDictionary even in cases where > the location is greater than th

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

Hi Daniel, > On 7 dec. 2015, at 23:11, Daniel A. Steffen wrote: > > FWIW I’ve updated the macosforge svn repo trunk to match with github > swift-corelibs-libdispatch trunk (sans the PRs, excecpt for my buildsystem > one), but going forward we are likely going to retire the macosforge > reposi

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

Alright, I've written up a proposal: https://github.com/apple/swift-evolution/pull/40 Feedback welcome! Jacob On Sat, Dec 5, 2015 at 2:25 PM, Jacob Bandes-Storch wrote: > On Sat, Dec 5, 2015 at 1:40 PM, Tony Parker > wrote: > >> One topic I wanted to discuss was finding a comprehensive list o