> Here, I also disagree. Imagine we are talking about an open-source library on
> GitHub. People will complain about the lack of sub-classability through
> issues and pull-requests. This will hopefully be enough to get discussions
> going on what is wrong with the API to warrant subclassing and exactly what
> the subclassing extension points should be. This discussion will happen
> around many libraries and will help educate people to think carefully about
> subclassing.
That's one of the false assumptions:
Many people don't want be lectured, but simply get their work done… as it has
been said before, this list is a quite exotic bubble, and it can be fatal to
assume that it is representative for the mass of developers that have to deal
with the consequences of its discussions.
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
