Re: [swift-evolution] Revisiting 0004, 0007 etc. - Swift deprecations

<swift-evolution@swift.org <mailto:swift-evolution@swift.org>> > Subject: Re: [swift-evolution] Revisiting 0004, 0007 etc. - Swift > deprecations > Message-ID: <d326ca33.b1738%jheer...@ucalgary.ca > <mailto:jheer...@ucalgary.ca>> > Content-Typ

Re: [swift-evolution] Revisiting 0004, 0007 etc. - Swift deprecations

> On Apr 3, 2016, at 8:51 PM, David Waite via swift-evolution > wrote: > > Swift also has the benefit of built-in access to C/C++ and in some > environments Objective-C code and libraries. This means it does not have to > strive to either replace or to have

Re: [swift-evolution] Revisiting 0004, 0007 etc. - Swift deprecations

> On Apr 3, 2016, at 1:25 PM, John Heerema via swift-evolution > wrote: > So, I’d ask “why is it so terrible that we’re going to remove it, even though > it presents an obstacle to developers coming over to Swift?” Maybe there’s a > really good answer to that, but

Re: [swift-evolution] Revisiting 0004, 0007 etc. - Swift deprecations

Thanks to all those who thoughtfully responded to this post! The folks who responded provided kind thoughts and advice. Ross O’Brian asked if I was familiar with the original discussion for 0004 and 0007. To answer: Yes, I read the discussions several times over a period of a few weeks before