[swift-evolution] [Proposal] Sealed classes by default

Goffredo Marocchi panajev at gmail.com
Sun Aug 14 06:26:03 CDT 2016

You are not familiar with us Italians and our love for (hopefully reasonable) arguing I see ;). I  commit to and accept the decision taken, but it remains a decision I disagree with and something that will probably birth a painful fork once say Android and/or other big corporations moved to Swift and decided for example that they wanted a new set of rules.

Sent from my iPhone

> On 14 Aug 2016, at 11:14, Jean-Daniel Dupas via swift-evolution <swift-evolution at swift.org> wrote:
>> Le 14 août 2016 à 11:17, John Holdsworth via swift-evolution <swift-evolution at swift.org> a écrit :
>> Hi folks,
>> I see from building the latest Swift-3.0 branch that I’m a little behind the times and this proposal has been accepted :(
>> https://github.com/apple/swift-evolution/blob/master/proposals/0117-non-public-subclassable-by-default.md
>> Is there no way we can revisit this decision? 60 emails on a mail group not read by the whole community
>> doesn’t quite seem enough validation for such a significant change to me.
> 60 emails ?  You’re joking. It is more 600 emails than 60 that was send about that proposal, and I’m pretty sure nobody want to see that discussion start again.
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160814/30507588/attachment.html>

More information about the swift-evolution mailing list