Casey Liss
I’m… not keen on the idea of final by default.
Do not want.
http://mjtsai.com/blog/2016/07/17/swift-classes-to-be-non-publicly-subclassable-by-default/ …
I side with @danielpunkass:https://twitter.com/danielpunkass/status/754818323708317696 …
-
@mbarriault Lattner acknowledged that there was *not* consensus among the community, so they were going with what the core team wanted.
Mike Barriault
Michael Tsai
@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
-
-
@mbarriault I think it’s a mistake to assume that the decision was based on the discussion. -
@mjtsai I'm just asking to see the other side of the discussion. I don't know why you're so intent on convincing me not to. -
@mbarriault I’m happy for you to read it. Not happy that you are assuming without reading that I was massively skewing the selection. -
@mjtsai I have read it. I'm reading it again, looking for a quote beyond the proposal authors that was actually for it. -
@mjtsai Every quote is either against or can't decide. -
@mjtsai If this was reflective of the full discussion, people would be more in arms about Lattner et al explicitly going against community - View other replies
-
@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. -
@mjtsai It does seem likely that, by the time Swift frameworks dominate, a Swift-ier solution will have presented itself. - View other replies
- Show more
-
-
-
@mjtsai Someone's collected against nicely in one thread so I don't have to dig through the mailing list. Only looking for the opposite. -
@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.
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.