Re: [swift-users] Protocol conformance failure

2017-03-21 Thread Slava Pestov via swift-users
Worth mentioning that @objc protocols do conform to themselves as long as they do not have static methods or initializer requirements. However this may be too heavy-handed if a simple overload can do the trick. Slava > On Mar 9, 2017, at 1:10 PM, Guillaume Lessard via swift-users > wrote: >

Re: [swift-users] Pointer conversions between different sockaddr types

2017-03-21 Thread Bouke Haarsma via swift-users
Hi all (again), It seems the fix is to (only) replace withUnsafePointer with withUnsafeMutablePointer twice. No need to apply the @escaping fixit even. -- Bouke On 2017-03-21 20:52:36 +, Bouke Haarsma via swift-users said: Hi Quinn, and others, I found that this code is still featured

Re: [swift-users] Pointer conversions between different sockaddr types

2017-03-21 Thread Bouke Haarsma via swift-users
Hi Quinn, and others, I found that this code is still featured on swift.org (https://swift.org/migration-guide/se-0107-migrate.html), but it doesn't compile anymore. There's a fix-it for adding @escaping, but also compile errors due to invalid casts. Can someone have a look at fixing this cod