Karoy Lorentey
Karoy Lorentey
Bumping to 1.2.0 acknowledging just how much work the rest of the new features in 1.1.0 is taking. (I'm hoping 1.2.0 will come soon after 1.1.0 though.)
> This would make it possible to encode with BitSet and then decode with SortedSet. Yes, but having equivalent codable representations for distinct types is at best a nice-to-have feature,...
Sure.
> Hm, the [MinimalEncoder/Decoder facility](https://github.com/apple/swift-collections/blob/41fe772f8828748ec292ed01a928740c4d8af2c5/Sources/_CollectionsTestSupport/MinimalTypes/MinimalDecoder.swift#L249) ought to catch such type mismatches. We'll need to take a look at what's going on. Ah, it's all good! This is on a `UInt.bitWidth...
Merged with changes in #208
Closing due to current lack of actionable work. Please reopen with a reproducer if this continues to be a problem.
The workaround for now is to manually add `libswiftCore.dylib` to the `_AtomicsShims` target's linked library list. The root cause is that the module relies on a couple of symbols exported...
@ckornher Thanks for reporting this issue! I believe it is now fixed on main. Please reopen if you can still reproduce it with the current head revision.
Unfortunately the fix triggered a compiler issue (https://bugs.swift.org/browse/SR-13708), so I'll need to revert it.
Thanks for the report! Unfortunately the reproduction steps don't contain enough information to debug this problem -- could you please provide a sample project that exhibits this issue?