<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=""><div><blockquote type="cite" class=""><div class="">On Jun 10, 2016, at 3:22 PM, Austin Zheng 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 dir="ltr" class=""><div class="">So, instead of:</div><div class=""><br class=""></div><div class=""><div class="">@available(*, unavailable, renamed:"someNewAPI()")</div><div class="">public func someOldAPI() -> Int { fatalError() }</div></div><div class=""><br class=""></div><div class="">You can just have:</div><div class=""><br class=""></div><div class=""><div class="">@available(*, unavailable, renamed:"someNewAPI()")</div><div class="">public func someOldAPI() -> Int</div></div><div class=""><br class=""></div><div class="">The intent is, in my opinion, clearer for the latter and it feels less kludgy.</div></div></div></blockquote></div><br class=""><div class=""><div class="">You ask, we answer. I'd much prefer spelling out <font face="Menlo" class="">{ fatalError("unavailable API") }</font>. </div><div class="">It makes the code clearer to read, to maintain, it produces debug and runtime errors. etc. I think </div><div class="">this is an example where concision is overrated.</div><div class=""><br class=""></div><div class="">-- E</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""></blockquote></div></div></body></html>