[swift-evolution] Final by default for classes and methods
matthew at anandabits.com
Wed Dec 23 10:53:58 CST 2015
> On Dec 23, 2015, at 10:51 AM, Felipe Cypriano via swift-evolution <swift-evolution at swift.org> wrote:
> I can't speak for the others but I join the list as a skeptical of this proposal and in one day I've embraced it. The benefits of it far out weight the fears of having it.
That’s great! Thank you so much for keeping an open mind and considering the arguments for their merit rather than having an emotional bias Felipe.
> I'd love to read it from the beginning but is kind of impossible.
> Felipe Cypriano
> On Dec 23, 2015, at 02:51, Tino Heth <2th at gmx.de <mailto:2th at gmx.de>> wrote:
>>> Isn't this proposal solving a problem that in practice doesn't exist or isn't common enough to be worth a language level fix? I'm trying to find an example of a common problem - in any language - that would benefit by having final/sealed by default.
>> I guess you share that attitude with most developers that have not read the full thread and never will do… and that is not meant as a suggestion to review all those posts;-): I don't think there is anything that will make someone change his opinion on this topic.
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution