<div dir="ltr">Got it. I&#39;ve seen the experimental thing elsewhere in the code. I&#39;ll work under the assumption that inconsistencies are experimental and I&#39;ll open bugs for things that are inconsistent but not marked as such.</div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jan 4, 2016 at 2:51 PM Tony Parker &lt;<a href="mailto:anthony.parker@apple.com">anthony.parker@apple.com</a>&gt; wrote:<br></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">Hi Ian,<div><br></div><div>Any place where the API differs should be marked with a comment like this:</div><div><br></div><div>/// - Experiment: This is a draft API currently under consideration for official import into Foundation</div><div><br></div><div>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">bugs.swift.org</a>. Most of the ‘Experiment’ APIs are something we have no alternative but to change, though.</div><div><br></div><div>Thanks for your work on this,</div><div>- Tony</div><div><br><div><blockquote type="cite"></blockquote></div></div></div><div style="word-wrap:break-word"><div><div><blockquote type="cite"><div>On Dec 21, 2015, at 5:39 PM, Ian Ynda-Hummel via swift-corelibs-dev &lt;<a href="mailto:swift-corelibs-dev@swift.org" target="_blank">swift-corelibs-dev@swift.org</a>&gt; wrote:</div><br></blockquote></div></div></div><div style="word-wrap:break-word"><div><div><blockquote type="cite"><div><div dir="ltr">I&#39;ve been working on <a href="https://bugs.swift.org/browse/SR-276" target="_blank">SR-276</a> and I&#39;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><br></div><div>corelib:</div><div>    <span>public</span><span> </span><span>func</span><span> URLByAppendingPathComponent(pathComponent: </span><span>String</span><span>) -&gt; </span><span>NSURL</span><span>?</span></div><div><span><br></span></div><div><span>OS X:</span></div><div><span>    </span><span>public</span><span> </span><span>func</span><span> URLByAppendingPathComponent(pathComponent: </span><span>String</span><span>) -&gt; </span><span>NSURL</span></div><div><span><br></span></div><div>That particular case seems to be a difference in the treatment of the return value from CFURL</div><div><br></div><div>   <span>public</span><span> </span><span>func</span><span> CFURLCreateCopyAppendingPathComponent(allocator: </span><span>CFAllocator</span><span>!, </span><span>_</span><span> url: </span><span>CFURL</span><span>!, </span><span>_</span><span> pathComponent: </span><span>CFString</span><span>!, </span><span>_</span><span> isDirectory: </span><span>Bool</span><span>) -&gt; </span><span>CFURL</span><span>!</span></div><div><span><br></span></div><div><span>Which briefly looking appears to be the same between corelib and OS X.</span></div><div><span><br></span></div><div><span>I&#39;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"><div><div><blockquote type="cite"><div><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">
_______________________________________________<br>swift-corelibs-dev mailing list<br><a href="mailto:swift-corelibs-dev@swift.org" target="_blank">swift-corelibs-dev@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-corelibs-dev" target="_blank">https://lists.swift.org/mailman/listinfo/swift-corelibs-dev</a><br></div></blockquote></div><br></div></div></blockquote></div>