<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="">Great, sounds good. If you ever notice a divergence, feel free to either file a bug or submit a PR that adds the comment. I don’t want to lose track of these things.<div class=""><br class=""></div><div class="">- Tony</div><div class=""><br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Jan 4, 2016, at 11:55 AM, Ian Ynda-Hummel <<a href="mailto:ianynda@gmail.com" class="">ianynda@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Got it. I've seen the experimental thing elsewhere in the code. I'll work under the assumption that inconsistencies are experimental and I'll open bugs for things that are inconsistent but not marked as such.</div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Mon, Jan 4, 2016 at 2:51 PM Tony Parker <<a href="mailto:anthony.parker@apple.com" class="">anthony.parker@apple.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">Hi Ian,<div class=""><br class=""></div><div class="">Any place where the API differs should be marked with a comment like this:</div><div class=""><br class=""></div><div class="">/// - Experiment: This is a draft API currently under consideration for official import into Foundation</div><div class=""><br class=""></div><div class="">If not, then we found some place that we either need to change or propose a change for. We can track those with bugs on <a href="http://bugs.swift.org/" target="_blank" class="">bugs.swift.org</a>. Most of the ‘Experiment’ APIs are something we have no alternative but to change, though.</div><div class=""><br class=""></div><div class="">Thanks for your work on this,</div><div class="">- Tony</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""></blockquote></div></div></div><div style="word-wrap:break-word" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 21, 2015, at 5:39 PM, Ian Ynda-Hummel via swift-corelibs-dev <<a href="mailto:swift-corelibs-dev@swift.org" target="_blank" class="">swift-corelibs-dev@swift.org</a>> wrote:</div><br class=""></blockquote></div></div></div><div style="word-wrap:break-word" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">I've been working on <a href="https://bugs.swift.org/browse/SR-276" target="_blank" class="">SR-276</a> and I'm finding a fair amount of inconsistencies between corelib Foundation and OS X Foundation. It seems to be most common with optionality of return values. e.g., in NSURL<div class=""><br class=""></div><div class="">corelib:</div><div class=""> <span class="">public</span><span class=""> </span><span class="">func</span><span class=""> URLByAppendingPathComponent(pathComponent: </span><span class="">String</span><span class="">) -> </span><span class="">NSURL</span><span class="">?</span></div><div class=""><span class=""><br class=""></span></div><div class=""><span class="">OS X:</span></div><div class=""><span class=""> </span><span class="">public</span><span class=""> </span><span class="">func</span><span class=""> URLByAppendingPathComponent(pathComponent: </span><span class="">String</span><span class="">) -> </span><span class="">NSURL</span></div><div class=""><span class=""><br class=""></span></div><div class="">That particular case seems to be a difference in the treatment of the return value from CFURL</div><div class=""><br class=""></div><div class=""> <span class="">public</span><span class=""> </span><span class="">func</span><span class=""> CFURLCreateCopyAppendingPathComponent(allocator: </span><span class="">CFAllocator</span><span class="">!, </span><span class="">_</span><span class=""> url: </span><span class="">CFURL</span><span class="">!, </span><span class="">_</span><span class=""> pathComponent: </span><span class="">CFString</span><span class="">!, </span><span class="">_</span><span class=""> isDirectory: </span><span class="">Bool</span><span class="">) -> </span><span class="">CFURL</span><span class="">!</span></div><div class=""><span class=""><br class=""></span></div><div class=""><span class="">Which briefly looking appears to be the same between corelib and OS X.</span></div><div class=""><span class=""><br class=""></span></div><div class=""><span class="">I'm not sure what the best way forward on these things is, though, as the corelib versions have seemed consistently improved, but presumably we still want maintain compatibility. Anyone have ideas?</span></div>
</div>
</div></blockquote></div></div></div><div style="word-wrap:break-word" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class=""><img src="https://u2002410.ct.sendgrid.net/wf/open?upn=U7z7oSqRMSwdl2rYt9JJ4zIFaeg4R-2FxExg9xndDuCbxSh4aH3-2B9KVV85Xddq-2BNqDZFUwtJxl08WJzNDtRt-2Bizd9YqlrdRlrzY7rTKfsXABLYww0gbZBlY8UPCBZKs4LQ5kAx41L48E-2FmC7ywLlfWhIAqJGMCKCqQj8JoJhzzvLadVq539XU7MfjkoecbCW2DQxEeOtpPHxC9K7VpTkzhymO-2FGpEe5PauTGcdwYvTxb4-3D" alt="" width="1" height="1" border="0" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important" class="">
_______________________________________________<br class="">swift-corelibs-dev mailing list<br class=""><a href="mailto:swift-corelibs-dev@swift.org" target="_blank" class="">swift-corelibs-dev@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-corelibs-dev" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev</a><br class=""></div></blockquote></div><br class=""></div></div></blockquote></div>
</div></blockquote></div><br class=""></div></div></body></html>