@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 them0 replies 0 retweets 0 likes -
@mbarriault I think it’s a mistake to assume that the decision was based on the discussion.0 replies 0 retweets 0 likes -
@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.0 replies 0 retweets 0 likes -
@mbarriault I’m happy for you to read it. Not happy that you are assuming without reading that I was massively skewing the selection.0 replies 0 retweets 0 likes -
@mjtsai I have read it. I'm reading it again, looking for a quote beyond the proposal authors that was actually for it.0 replies 0 retweets 0 likes -
@mjtsai Every quote is either against or can't decide.0 replies 0 retweets 0 likes -
@mjtsai If this was reflective of the full discussion, people would be more in arms about Lattner et al explicitly going against community0 replies 0 retweets 0 likes -
@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.0 replies 0 retweets 0 likes -
@mjtsai It does seem likely that, by the time Swift frameworks dominate, a Swift-ier solution will have presented itself.0 replies 0 retweets 0 likes
@mbarriault Maybe the ones designed with the least care, default closed classes all the way, will be those most in need of overriding?
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.
Michael Tsai
Mike Barriault