<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 22, 2016, at 12:42 PM, Dave Abrahams via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><br style="font-family: Palatino-Roman; font-size: 14px; 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;" class=""><span style="font-family: Palatino-Roman; font-size: 14px; 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; float: none; display: inline !important;" class="">on Fri Jul 22 2016, Ben Rimmington <</span><a href="mailto:swift-evolution@swift.org" style="font-family: Palatino-Roman; font-size: 14px; 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;" class="">swift-evolution@swift.org</a><span style="font-family: Palatino-Roman; font-size: 14px; 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; float: none; display: inline !important;" class="">> wrote:</span><br style="font-family: Palatino-Roman; font-size: 14px; 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;" class=""><br style="font-family: Palatino-Roman; font-size: 14px; 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;" class=""><blockquote type="cite" style="font-family: Palatino-Roman; font-size: 14px; 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;" class=""><blockquote type="cite" class="">On 21 Jul 2016, at 18:02, Michael Gottesman wrote:<br class=""><br class="">This is a proposal to move AutoreleasingUnsafeMutablePointer from<br class="">StdlibCore to the Objective C overlay. The reason to do this is that<br class="">ideally StdlibCore would not have any code specific to ObjC in<br class=""></blockquote><br class=""><blockquote type="cite" class="">it. This is a small step that we can take in this direction by<br class="">moving the public API of AutoreleasingUnsafeMutablePointer to the<br class="">ObjC overlay. The way that this would be done is that the<br class="">implementation for AutoreleasingUnsafeMutablePointer would remain in<br class="">StdlibCore, but we would add an underscore to make that API private<br class="">to the standard library. Then inside the ObjC overlay, we would<br class="">create a typealias to the internal API with the non-underscored name<br class="">(i.e. make the typealias the public API). Then at a later point in<br class="">time we can move the implementation. The reason why I am not<br class="">proposing to move the implementation today is that there are<br class="">dependencies in Array/Hashed Collections on<br class="">AutoreleasingUnsafeMutablePointer. Moving that code is a larger<br class="">project that is preconditioned on this proposal going in first as an<br class="">incremental step.<br class=""></blockquote><br class="">If you want to move APIs which aren't cross-platform out of stdlib,<br class="">should there be a similar proposal for the PlaygroundQuickLook enum<br class="">and CustomPlaygroundQuickLookable protocol?<br class=""><br class=""><<a href="https://github.com/apple/swift/blob/master/stdlib/public/core/Mirror.swift" class="">https://github.com/apple/swift/blob/master/stdlib/public/core/Mirror.swift</a>><br class=""><br class=""><<a href="https://github.com/apple/swift-xcode-playground-support" class="">https://github.com/apple/swift-xcode-playground-support</a>><br class=""></blockquote><br style="font-family: Palatino-Roman; font-size: 14px; 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;" class=""><span style="font-family: Palatino-Roman; font-size: 14px; 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; float: none; display: inline !important;" class="">That is a good question! We don't have an obvious existing module into</span><br style="font-family: Palatino-Roman; font-size: 14px; 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;" class=""><span style="font-family: Palatino-Roman; font-size: 14px; 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; float: none; display: inline !important;" class="">which to move them, though, do we?</span><br style="font-family: Palatino-Roman; font-size: 14px; 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;" class=""></div></blockquote></div><div class=""><br class=""></div><div class="">This philosophy appeals to me, especially when considering Swift as a </div><div class="">cross-platform language. Would you all be open to "new module" proposals?</div><div class="">Would that be internal or through Swift Evolution? I'm thinking also of</div><div class="">the discussion about creating a Swift native Math module w/ JordanR and</div><div class="">Steve C for things that don't belong in the stdlib but would be nice to have around,</div><div class="">sanctioned native modules.</div><div class=""><br class=""></div><div class="">As for PlaygroundSupport, how does that tie into stdlib? I thought it was its own </div><div class="">thing, separate from stdlib. Wouldn't both quick look and lookable belong there?</div><div class=""><br class=""></div><div class="">-- E</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class=""><br class=""></div></div></body></html>