<div dir="ltr">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")</div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Oct 8, 2016 at 9:22 AM, Lou Zell <span dir="ltr"><<a href="mailto:lzell11@gmail.com" target="_blank">lzell11@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi all,</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Is there a creative way to use UIViews, but with the dependency on NSCoding removed? I am open to total hacks.</div><div><br></div><div>Thanks!</div><span class="HOEnZb"><font color="#888888"><div>Lou</div><div><br></div></font></span></div>
</blockquote></div><br></div>