<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On May 9, 2016, at 7:38 PM, Rod Brown via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><blockquote type="cite" class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></blockquote></div></blockquote><div class=""><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><div class=""><blockquote type="cite" class=""><font class="">I am uncertain about the NSCoding proposition as it is not a generic concept that is platform agnostic. It is a baked in, Objective-C, Apple-only paradigm that seems to me should retain it’s NS prefix.</font></blockquote></div></div></div></div></div></div></div><br class=""><div class="">Plus, NSCoding has a *lot* of legacy cruft associated with it that we would do well to jettison with a brand-new coding protocol, IMO.</div><div class=""><br class=""></div><div class="">Charles</div><div class=""><br class=""></div></body></html>