Now we have AnyHashable, NSUniqueObject in the archiver can go. I’ll file a PR.
— Luke
> On 11 Aug 2016, at 4:29 AM, Tony Parker via swift-dev
> wrote:
>
> We have fixes ready to go for this keyed archiver issue but the inability to
> get past CI has slowed us down on putting it in.
>
> - To
We have fixes ready to go for this keyed archiver issue but the inability to
get past CI has slowed us down on putting it in.
- Tony
> On Aug 9, 2016, at 12:02 PM, Joe Groff via swift-dev
> wrote:
>
>>
>> On Aug 4, 2016, at 1:21 PM, Philippe Hausler via swift-dev
>> wrote:
>>
>> With a fr
> On Aug 4, 2016, at 1:21 PM, Philippe Hausler via swift-dev
> wrote:
>
> With a freshly built toolchain from ToT swift, building ToT
> swift-corelibs-foundation I am getting some very strange failures in the unit
> tests:
>
> Test Suite 'TestNSKeyedArchiver' started at 13:15:01.843
> Test C
Not post facto of pushing it. I could not in good conscience push such a large
change without making certain the tests passed. It was extractable but I squash
merged back onto master to avoid conflicts.
Sent from my iPhone
> On Aug 8, 2016, at 10:42 PM, Luke Howard wrote:
>
> Would it be poss
Would it be possible to separate the change to NSKeyedUnarchiver in 1d1ddba9
into a separate commit?
> On 5 Aug 2016, at 6:21 AM, Philippe Hausler via swift-dev
> wrote:
>
> With a freshly built toolchain from ToT swift, building ToT
> swift-corelibs-foundation I am getting some very strange
With a freshly built toolchain from ToT swift, building ToT
swift-corelibs-foundation I am getting some very strange failures in the unit
tests:
Test Suite 'TestNSKeyedArchiver' started at 13:15:01.843
Test Case 'TestNSKeyedArchiver.test_archive_array' started at 13:15:01.843
assertion failed: f
