1

Hello,

I support the proposal to introduce abstract classes to Swift. I agree with what has been said about inheritance still being an important feature (despite going slightly out off fashion) and this will make it more useful.

I am just wondering if it is really necessary to have the requirement about having to declare a class as abstract if it "contains one or more abstract methods/properties” as suggested in the proposal. Can’t we just consider the class as abstract as soon as there is at least one unimplemented abstract method/property? Furthermore, do we really need the keyword “abstract” as modifier of a class?

Regards,

Mirek

2

I'd prefer to see instantly whether a class is abstract or not. Furthermore it is very useful to declare a base class as abstract even if none of its members is abstract.

-Thorsten

···

Am 26.02.2016 um 22:25 schrieb Mirek Petricek via swift-evolution <swift-evolution@swift.org>:

Hello,

I support the proposal to introduce abstract classes to Swift. I agree with what has been said about inheritance still being an important feature (despite going slightly out off fashion) and this will make it more useful.

I am just wondering if it is really necessary to have the requirement about having to declare a class as abstract if it "contains one or more abstract methods/properties” as suggested in the proposal. Can’t we just consider the class as abstract as soon as there is at least one unimplemented abstract method/property? Furthermore, do we really need the keyword “abstract” as modifier of a class?

Regards,

Mirek
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution