> - Slippery Slope: SE-0117 adds yet another entry to the already huge list of
> things in Swift that subtly or openly discourage people from subclassing. How
> far are we from someone seriously proposing to outright rip inheritance out
> of the language? Enough is enough. Stop with the
>
> * What is your evaluation of the proposal?
> * If you have used other languages or libraries with a similar feature,
> how do you feel that this proposal compares to those?
Extremely strong -1.
I understand the performance benefit, but it’s extremely problematic if you’ve
used
So here’s my 2 cents. I talked to Charles about this off list, so I’ll just say
my piece and then move along. :)
It seems to me that ErrorType is very empty because it’s meant to be a
placeholder in the language for whatever the native error type is on the
platform. When I’m in
