> On Nov 16, 2017, at 3:30 PM, Ian Partridge wrote:
>
>> Is the Foundation test suite run against both implementations to attempt to
>> catch these kinds of things?
>> If not it would seem like a big win to do so.
>
> Not yet, but there is work underway to do this. See
> https://github.com/app
> On Nov 16, 2017, at 2:57 PM, Alex Blewitt wrote:
>
> I understood your question, but I can only point to you as to what is
> available and run on the swift-corelibs-foundation open source project.
Sorry to continue on this train (especially since it’s a big of a derailment).
I’m really not t
> On Nov 16, 2017, at 2:02 PM, Alex Blewitt wrote:
>
> There is a TestFoundation target in the swift-corelibs-foundation project,
> which can allow the tests to be run against the open source codebase.
Sorry, maybe I wasn’t clear, I was wondering if there’s a test suite that
regularly runs aga
Brandon Williams and I have come across a lot of inconsistencies between
Foundations in our Swift web work. We’ve been trying to file bugs when we
remember to, but I’m curious if there’s a better way to catch these. Is the
Foundation test suite run against both implementations to attempt to catc
Seems to me that anything with `-compare:` could conform to Comparable. The
list, however, is surprisingly short, and half bridge over to native Swift
types that are already Comparable:
- [NSDate compare:]
- [NSIndexPath compare:]
- [NSNumber compare:]
- [NSString compare:]
Looks like NSIndexPa
