Re: [swift-corelibs-dev] Inconsistencies between Foundation APIs

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. - Tony > On Jan 4, 2016, at 11:55 AM, Ian Ynda-Hummel wrote: > > Got it. I've seen the experimental thing elsewhere in the code

Re: [swift-corelibs-dev] Inconsistencies between Foundation APIs

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. On Mon, Jan 4, 2016 at 2:51 PM Tony Parker wrote: > Hi Ian, > > Any place where the API

Re: [swift-corelibs-dev] Inconsistencies between Foundation APIs

Hi Ian, Any place where the API differs should be marked with a comment like this: /// - Experiment: This is a draft API currently under consideration for official import into Foundation If not, then we found some place that we either need to change or propose a change for. We can track those

[swift-corelibs-dev] Inconsistencies between Foundation APIs

I've been working on SR-276 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 corelib: public func URLByAppendingPathComponent(path