SE-0304 (4th review): Structured Concurrency

[benrimmington]

@Ben_Cohen

This general problem – of being able to distinguish an initializer purely with a marker – has come up before in an evolution proposal, though unfortunately I can't recall which one.

You might be thinking of SE-0104, but that was for methods rather than initializers.

[Re-Review] SE-0104: Protocol-oriented integers

For the review, Dave asked me to raise a design question on his behalf, since he's on vacation. There are places where the proposal introduces one-case types as a labeling mechanism to distinguish different operations with otherwise the same argument names, for instance: public enum ReportingOverflow { case reportingOverflow } protocol Number {   func adding(_ other: Self) -> Self } protocol FixedWidthInteger: BinaryInteger {   func adding(_ other: Self, _: ReportingOverflow) -> (partialVa…

[Re-Review] SE-0104: Protocol-oriented integers

Hi everyone, The core team met and reviewed the discussion of this proposal so far, and had the following mid-review feedback to relay back to the list: Regarding the “Number” protocol: it was felt this is likely to cause confusion with NSNumber, given the NS-prefix-dropping versions of other Foundation types indicate a value-typed concrete type equivalent, which this won’t be. The recommendation is to use “Numeric" instead. Regarding the question of the trailing argument to distinguish overf…