<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 7, 2015, at 10:56 AM, Jan Neumüller via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Alegreya-Regular; font-size: 15px; font-style: normal; font-variant: 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="">But what overhead? As you know Swift has *NO* exceptions. It’s just syntax sugar for normale error values.</span><br class="Apple-interchange-newline"></div></blockquote></div><br class=""><div class="">Mostly the overhead in the caller of having to pass a (hidden) error parameter into the call, and check the return value and branch afterwards.</div><div class=""><br class=""></div><div class="">(C++/Obj-C exceptions actually have no runtime cost in the normal success case; it’s only <i class="">throwing</i> an exception that’s expensive.)</div><div class=""><br class=""></div><div class="">—Jens</div></body></html>