> • What is your evaluation of the proposal?
Good stuff.
How exact does the type match have to be? Can they be two subclasses of a
different superclass? Can they conform to common protocols? Can they conform to
no common protocols and just be `AnyObject` or `Any`?
Is there a way to specify the type, either to get an exact match or just to ask
or a supertype? If you do that, does it have to be specified on both, or only
one? Something like:
case let .Case1(x: SignedIntegerType, 2), let .Case2(2, x):
> • Is the problem being addressed significant enough to warrant a change
> to Swift?
It's a minor concern, but still very helpful to fix.
> • Does this proposal fit well with the feel and direction of Swift?
Yes.
> • If you have used other languages or libraries with a similar feature,
> how do you feel that this proposal compares to those?
I don't believe I have. It's nice.
> • How much effort did you put into your review? A glance, a quick
> reading, or an in-depth study?
Quick reading.
--
Brent Royal-Gordon
Architechies
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
