I wonder if it will run on Swift server framework instead of Apache since
they shown to have better performance and memory efficient than Apache.
___
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users
This is a wrong place to ask. This topic is part of the iOS SDK from Apple not
part of Swift itself or libraries like Foundation.
--
Adrian Zubarev
Sent with Airmail
Am 8. Oktober 2016 um 18:32:50, Lou Zell via swift-users
(swift-users@swift.org(mailto:swift-users@swift.org)) schrieb:
>
> O
Oh wow, I stumbled on this immediately after posting: For anyone else that
fills their NSCoding initializers with assert(false), switch them to
fatalError("message")
On Sat, Oct 8, 2016 at 9:22 AM, Lou Zell wrote:
> Hi all,
>
> For better or worse I still hand code most of my views. I am getting
Hi all,
For better or worse I still hand code most of my views. I am getting
frustrated by the constant compiler error that I haven't updated "required
init(coder:)", which is something that will never be executed in my case.
Is there some hacky mechanism that I could use to create a subtype that
Oh thanks, I fundamentally misunderstood how unwrapped optionals work.
On Fri, Oct 7, 2016 at 6:25 PM, Joe Groff wrote:
>
>> On Oct 7, 2016, at 7:02 AM, Ingo Maier via swift-users
>> wrote:
>>
>> Is there a way in Swift 3 to pass a null pointer to a C function that
>> takes an implicitly unwrap
