[swift-users] ideas to remove NSCoding as requirement in UIView subclasses

[Adrian Zubarev]

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 at swift.org(mailto:swift-users at swift.org)) schrieb:

> 
> 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 <lzell11 at gmail.com(mailto:lzell11 at gmail.com)> wrote:
> > 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 doesn't conform to all protocols of the parent? Seems like recipe for disaster so I suspect it's not built into swift directly. 
> > 
> > Is there a creative way to use UIViews, but with the dependency on NSCoding removed? I am open to total hacks. 
> > 
> > Thanks! 
> > Lou
> > 
> 
> _______________________________________________
> swift-users mailing list
> swift-users at swift.org
> https://lists.swift.org/mailman/listinfo/swift-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-users/attachments/20161008/f1b2b246/attachment.html>