@jckarter So it’s less useful for the cases I’m talking about doing things unexpected by the API designer.
@jckarter bad decision. Whereas the framework client, without the ability to override, has no recourse.
@jckarter If this is about 3rd party frameworks, the vendor can always put a breaking change in a new version. If necessary to reverse a
@jckarter I mean in general—undocumented/unpromised subclassing details and non-subclassing-related bugs.
@austinzheng So fear is that either there is no good answer or they don’t care.
@austinzheng The issue to me is that we know they’re smart, but they have failed to allay the concerns.
@jckarter Aha, that makes sense. So then you either force a recompile or can’t optimize.
@jckarter I don’t understand why you have to support bugs (rather than the promised contract) forever. Why not warn like with deprecation?
@jckarter I would have thought you could revoke a final across a module boundary because clients can’t inline, anyway.
@jckarter You’re saying no change for Apple Swift frameworks because you consider the API, but it’s about protecting others who don’t?
@jckarter Right, but presumably you expect that to ultimately benefit end users (indirectly).
And, trying to copy Xcode 8b3 to the other Mac, got my regular reminder that AirDrop works less than half the time.
@jmfd I’ve done that, but then a couple times I forgot to launch it and later found that my iPhone didn’t have access to the latest files.
Isn’t there some way that Dropbox can see I’m unarchiving Xcode 8 outside its folder and ignore those file system events without 150% CPU?
Wondering whether 10.11.6 will finally fix the bug where newly attached drives don’t auto-mount.
@adamkaump I personally see those as hypothetical small wins measured against serious problems for which no one has answers.
@adamkaump Thanks. That’s pretty much what other people in favor have been saying.
@teddybeardog777 It eventually fixed itself, but I’m not sure what I did. Maybe restart.
@adamkaump Because…you think the concerns about bugs and innovation are overblown? Outweighed? Some other reason?
@mbarriault Maybe the ones designed with the least care, default closed classes all the way, will be those most in need of overriding?
@mbarriault I think people are not up in arms b/c this was long the expected result and impact is limited b/c only affects Swift classes.
@mbarriault Most of the +1 responses were basically paraphrases of the first two quoted paragraphs from the proposal.
@mbarriault I wasn’t trying to balance in terms of votes but to include the main points that were raised.
@mbarriault I’m happy for you to read it. Not happy that you are assuming without reading that I was massively skewing the selection.
@mbarriault That was me. I didn’t intend to only collect against. In fact, some are from +1 replies. And I include the proposal’s co-author.
@mbarriault I think it’s a mistake to assume that the decision was based on the discussion.
@mbarriault Lattner acknowledged that there was *not* consensus among the community, so they were going with what the core team wanted.
@mbarriault I don’t see how you could read the discussion and think there was consensus.