<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 Darwin, we can say:<div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">import Foundation</div><div class="">exit(2)</div></blockquote><br class=""><div class="">I'm not totally sure how this works, since exit is provided by Darwin, not by Foundation. &nbsp;But somehow importing Foundation imports Darwin as well.</div><div class=""><br class=""></div><div class="">I think for source compatibility, we should support this, because&nbsp;<a href="http://stackoverflow.com/questions/34186994/swift-2-2-on-linux-use-of-unresolved-identifier-exit" class="">people</a>&nbsp;are&nbsp;<a href="http://stackoverflow.com/questions/24102157/seeking-an-exit-equivalent-in-swift" class="">asking</a>&nbsp;why it doesn't work out of the box.</div><div class=""><br class=""></div><div class="">I considered PRing an exit implementation in corelibs-foundation, but I think that might cause the opposite problem–introduce a conflict between Darwin/Glibc exit and Foundation "exit".</div><div class=""><br class=""></div><div class="">Can someone speak to how this is solved in Darwin Foundation and what we should do about it?</div></body></html>