<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="">Le 20 janv. 2017 à 05:07, Saagar Jha via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; 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="">Looks pretty good in general from my quick glance–at least, it’s much better than the current situation. I do have a couple of comments and questions, which I’ve inlined below.</span><div class="" style="font-family: Helvetica; font-size: 12px; 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;"><br class=""><div class=""><div class="" style="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; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Saagar Jha</div></div><br class=""><div class=""><blockquote type="cite" class=""><div class="">…</div></blockquote><div class=""><br class=""></div><div class="">Any reason why Locale is defaulted to nil, instead of currentLocale? It seems more useful to me.</div></div></div></div></blockquote></div><div class=""><br class=""></div><div class=""><br class=""></div>Don’t know the rational here, but it may prevent a lots of bugs.<div class="">Having a call that behave differently depending the system locale is a pain. I can’t recall how many time I had ti fix tests cases because they where implicitly relying on the default locale.</div><div class="">It also caused many issue with scanning and formatting non localized values as you have to explicitly specify a neutral local which is usually not properly done by the developers.</div><div class=""><br class=""></div></body></html>