<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Nevin,<div class=""><br class=""></div><div class="">Thanks for taking the time to review the proposal!<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Dec 20, 2017, at 7:08 PM, Nevin Brackett-Rozinsky 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=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Alternatively, since the “@abiPublic” attribute allows objects to be used by inlined code, why not spell it “@inlinable”?</div><br class="Apple-interchange-newline"></div></blockquote></div><br class=""><div class="">Because both @abiPublic and @inlinable can be applied to functions, and we really do need to distinguish the two cases — they’re definitely not the same:</div><div class=""><br class=""></div><div class="">private func pf() {}</div><div class=""><br class=""></div><div class="">@abiPublic func af() {</div><div class=""> pf() // OK — we can reference a private function here</div><div class=""> // framework author can change the body of af() and clients see the new body</div><div class="">}</div><div class=""><br class=""></div><div class="">@inlinable public func if() {</div><div class=""> pf() // error!</div><div class=""><br class=""></div><div class=""> af() // OK</div><div class=""><br class=""></div><div class=""> // changes made here don’t necessarily get picked up by clients until recompiled</div><div class="">}</div><div class=""><br class=""></div><div class="">Slava</div></div></body></html>