Re: [swift-dev] [swift-evolution] End of source-breaking changes for Swift 3

I noticed that while SE-0091 appears to be implemented (from a cursory glance at some of the affected types like Equatable and String), it looks like the named methods are still part of the FloatingPoint protocol and they still use global operators. Is anyone tracking the migration of that protoco

Re: [swift-dev] [swift-evolution] End of source-breaking changes for Swift 3

On Wed, Jul 27, 2016 at 3:58 PM Dave Abrahams wrote: > > on Wed Jul 27 2016, Ted Kremenek wrote: > > > - swift-evolution, swift-evolution-announce > > > > Dave/Max: can you speak this? > > >> On Jul 27, 2016, at 3:17 PM, Tony Allevato wrote: > >> > >> I noticed that while SE-0091 appears to be

Re: [swift-dev] Build Failure with Xcode 9.0 beta 5

Not that it's something that I'd generally recommend, but I ended up just commenting out that #import in AVFoundation.h and the build was able to complete successfully (enough for what I needed). Since the only thing I'm currently using Xcode 9 beta for is building Swift and I'm not doing anything

Re: [swift-dev] [swift-evolution] [Question] Absolute paths in executable .swiftmodule files

Thanks for bringing this up, Pepper! We have many of the same issues with our Swift support in Bazel ; since .swiftmodule files aren't hermetic, we can't reliably cache them. The proliferation of import paths in the modules is another major issue—as part of our

Re: [swift-dev] [swift-evolution] Re-pitch: Deriving collections of enum cases

On Sun, Nov 5, 2017 at 11:54 PM Jacob Bandes-Storch via swift-evolution < swift-evolut...@swift.org> wrote: > Over a year ago, we discussed adding a magic "allValues"/"allCases" static > property on enums with a compiler-derived implementation. The original > proposal > PR

Re: [swift-dev] [swift-evolution] Re-pitch: Deriving collections of enum cases

On Fri, Nov 10, 2017 at 11:01 PM Xiaodi Wu via swift-evolution < swift-evolut...@swift.org> wrote: > On Sat, Nov 11, 2017 at 12:15 AM, Brent Royal-Gordon via swift-evolution < > swift-evolut...@swift.org> wrote: > >> > Personally I like the flexibility provided by the associatedtype, but I >> also

Re: [swift-dev] [swift-evolution] Re-pitch: Deriving collections of enum cases

On Sat, Nov 11, 2017 at 10:28 AM Xiaodi Wu wrote: > On Sat, Nov 11, 2017 at 11:23 AM, Tony Allevato > wrote: > >> >> >> On Fri, Nov 10, 2017 at 11:01 PM Xiaodi Wu via swift-evolution < >> swift-evolut...@swift.org> wrote: >> >>> Nit: if you want to call it `ValueEnumerable`, then this should be

Re: [swift-dev] [swift-evolution] Re-pitch: Deriving collections of enum cases

On Sat, Nov 11, 2017 at 1:53 PM Xiaodi Wu wrote: > On Sat, Nov 11, 2017 at 3:15 PM, Tony Allevato > wrote: > >> >> >> On Sat, Nov 11, 2017 at 10:28 AM Xiaodi Wu wrote: >> >>> On Sat, Nov 11, 2017 at 11:23 AM, Tony Allevato >> > wrote: >>> On Fri, Nov 10, 2017 at 11:01 PM Xiaodi W

Re: [swift-dev] Default deployment target for swiftc

I agree, the currently running OS seems like the right default here. Progressive disclosure and ease of prototyping are good motivations here. If I just want to quickly prototype something, I'm not going to be thinking about choosing a minimum OS; I'm just going to write something using the APIs th

Re: [swift-dev] State of String: ABI & Performance

On Thu, Jan 11, 2018 at 12:32 PM Michael Ilseman via swift-dev < swift-dev@swift.org> wrote: > Hi Chris! > > +CC Michael Gottesman, as I veer into talking about ARC. > > > On Jan 10, 2018, at 9:29 PM, Chris Lattner wrote: > > On Jan 10, 2018, at 11:55 AM, Michael Ilseman via swift-dev < > swift-d