Casey LissVerified account

@caseyliss Is there a conveniently collected list of quotes arguing for externally final by default?

@mbarriault @mjtsai’s writeup is relatively even. The one I linked in my tweet.

@caseyliss That's not even. That's almost entirely against, and ignores that it was the community consensus, not big boss Apple.

@mbarriault I don’t see how you could read the discussion and think there was consensus.

@mjtsai There must've been if they accepted the proposal. The whole process was based on consensus. I've now read the arguments against...

@mbarriault Lattner acknowledged that there was *not* consensus among the community, so they were going with what the core team wanted.

@mjtsai Fair enough, but furthering the fact that clear the for arguments must've been as well-formed as against. I just want to read them

@caseyliss @danielpunkass I think I’m for this change. I avoid ad hoc framework subclassing in Objective-C, as it often feels fragile.

@caseyliss @danielpunkass Having to fix framework classes is tragic, and if there’s a bug that no one can get around without subclassing…

@caseyliss @danielpunkass then it should be very clear how useless it is until fixed and hopefully Apple has to be more proactive.

@caseyliss @danielpunkass not sure I like the idea of final at all. It’s like “nurrr I’ve perfected this class, you can’t improve it ”

@rennarda @caseyliss @danielpunkass That is probably supposed to mean: “Please, please, please consider what you are doing first..”

@Patrick_Lind I’d be OK with a warning, but “Any attempt to subclass a final class is reported as a compile-time error.”