>> 5) Prototyping. This should also not influence the decision about what the
>> default is for production code. I would not have a problem with a
>> prototyping environment allowing `inheritable` by default (maybe a
>> Playground mode?). There could even be a tool that migrates the prototype
>> to a real project and adds the `inheritable` annotation where necessary.
>> Regardless of what happens here, the prototyping problem can and should be
>> solved independently of the production language and should not influence the
>> default is used in and impacts production code.
Now, that offers an easy way out: Just assume that Swift stays in
prototype-mode (nothing lasts as long as a prototype) and write that migration
tool to annotate each class with final — problem solved, everyone is happy.
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
