Re: [swift-users] How to create an uninitialized pointer in Swift 3

Thank you so much. That's exactly what I needed! Lane ___ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users

Re: [swift-users] SPM: Subfolders in a Module

Ok, thank you very much! Best regards Toni > Am 16.09.2016 um 07:26 schrieb Ankit Agarwal : > > > > On Fri, Sep 16, 2016 at 12:21 AM, Toni Suter via swift-users > > wrote: > Hi everyone, > > Let's assume there's a Swift

[swift-users] open/public protocol with not overridable default implementation in the future?

I always wanted a way to make some protocol default implementations not overridable. Now Swift 3 got open vs. public behavior for classes. (Hopefully the inconsistency will be fixed soon and we’ll get open protocols as well.) Imagine this scenario with open/public protocols. // Module A //

Re: [swift-users] Problem calling a C function passing a void** from Swift 3

On 15 Sep 2016, at 22:11, Lane Schwartz via swift-users wrote: > Can anyone help me get the equivalent functionality in Swift 3? I think the main issue here is that, in Swift 3, unsafe pointers, in their various flavours, don’t explicitly support nil. Rather, nil is

Re: [swift-users] Vague error description when trying to match an instance in a switch statement

On 15 Sep 2016, at 19:53, hello--- via swift-users wrote: > It would be nice if the error message could be improved to spare confusion for > the other developers. Indeed. If you can file a bug about this, that’d be grand. Share and Enjoy --

Re: [swift-users] How to create an uninitialized pointer in Swift 3

In Swift 3, COpaquePointer was renamed to OpaquePointer, and nullable pointers are represented by optionals: SE-0055 – Make unsafe pointer nullability explicit using Optional https://github.com/apple/swift-evolution/blob/master/proposals/0055-optional-unsafe-pointers.md So the following