Karoy Lorentey
Karoy Lorentey
Xcode 14.2 requires macOS 12.5, just like Xcode 14.0.
Yes, I very intentionally omitted `Deque.capacity`, until I see a valid use case of it. All code I've seen that tries to make decisions about shrinking storage based on `capacity`...
Yes! Now that we have `Dictionary`, `OrderedDictionary`, `TreeDictionary` (and soon `SortedDictionary`, which isn't quite ready for use yet), I think we have enough examples of dictionary types to start forming...
My initial instinct is that this feature would not be a good fit with the `Deque` we have, i.e., one that implements copy-on-write value semantics. The headlining feature of Swift’s...
If pressed, it would be possible to expose a fixed-capacity deque variant as a new class type, possibly even rewriting the existing `Deque` to use it as its internal storage...
Note: my recommendation that the feature that distinguishes `debugDescription` from `description` is that the former's result must not cause confusion when embedded in structured syntax is not yet official --...
We decided to insert [a new interim release](https://github.com/apple/swift-system/issues/163) before these changes, which will use up the planned 1.3.0 version number. The changes originally targeting 1.3.0 will actually ship in 1.4.0,...
Interesting! I am not a Swift grammar expert, but to my naive, innocent eyes this does look like a better match with `InOutExpr` in AST. Not sure who would be...
@swift-ci test
Hm; dropping this from the 1.1.1 milestone, as we do not have a shipping Swift compiler that understands `@retroactive` yet.