[43] draft update

Author: jessesquires

_drafts/2016-10-20-issue-43.md

@@ -4,7 +4,7 @@ title: ! 'Issue #43'
 author: jsq
 ---
 
-Remember [SE-0025](https://github.com/apple/swift-evolution/blob/master/proposals/0025-scoped-access-level.md)? That's the proposal that controversially introduced `fileprivate`. However, if you're regretting this change (like me), then you might have another chance to be heard! See the mailing list discussion in this issue for details.
+Remember [SE-0025](https://github.com/apple/swift-evolution/blob/master/proposals/0025-scoped-access-level.md)? That's the proposal that controversially introduced `fileprivate`. However, if you're regretting this change (like me), then you might have another chance to be heard! See the mailing list discussion in this issue for details. This issue also covers "id-as-Any" and continues the on-going discussion about what should be considered a source-breaking change.
 
 <!--excerpt-->
 
@@ -14,12 +14,27 @@ Remember [SE-0025](https://github.com/apple/swift-evolution/blob/master/proposal
 
 ### Community
 
+There's a new post &mdash; [*Objective-C id as Swift Any*](https://developer.apple.com/swift/blog/?id=39) &mdash; on the official Apple Developer Swift blog. It clearly explains the changes in Swift 3.0 regarding Objective-C `id` importing into Swift as `Any` instead of `AnyObject`. If you've been confused about this, the post should clear things up!
+
 If you are contributing to or interested in LLVM, the [LLVM Developers' Meeting](http://llvm.org/devmtg/2016-11/) is coming up on November 3-4.
 
 ### Commits and pull requests
 
+Rintaro Ishizaki has submitted a [pull request](https://github.com/apple/swift/pull/5290) to fix [SR-2843](https://bugs.swift.org/browse/SR-2843). The theme of "is this a source-breaking change" returns!
+
+> In type parsing, `P1 & P2.Type` was parsed as `(metatype (composition P1 & P2))` and accepted.
+On the other hand, in expression position, `(P1 & P2.Type).self` was converted to just `P1` (`P2.Type` was silently discarded).
+> This PR fixes this problem, while keeping *source compatibility* to the current behavior.
+That said, expr:`(P1 & P2.Type).self` as type:`P1` is just a bug. IMO, no need to keep this behavior.
+
 Back in June, Austin Zheng [rewrote](https://github.com/apple/swift/pull/3046) native hashed collection indices, refactoring `Dictionary` and `Set`. This week, Alexis Beingessner took over and [rebased](https://github.com/apple/swift/pull/5291) the pull request and resolved conflicts. Despite some behavior differences and possible bridging performance regressions, it looks like the changes bring a lot of structural improvements to the code.
 
+Greg Parker submitted a [pull request](https://github.com/apple/swift/pull/5282) for a new reference count representation (work-in-progress). Based on the [benchmarks](https://github.com/apple/swift/pull/5282#issuecomment-253705039) noted by **@swift-ci**, there seem to be quite a few regressions &mdash; but I'm sure these will be fixed before merging!
+
+Dave Abrahams made a [small tweak](https://github.com/apple/swift/pull/5267) to (hopefully) speed up `Set`/`Dictionary` initialization from a `Sequence`.
+
+Doug Coleman opened a [pull request](https://github.com/apple/swift/pull/5048) to make the `utils/update-checkout` python script run in parallel. 😎 This should be useful for contributors.
+
 From this week's [LLVM weekly](http://llvmweekly.org/issue/146), a [lengthy proposal](https://reviews.llvm.org/rL284077) on moving LLVM to GitHub was added. As mentioned before, having all of these projects on GitHub could be beneficial to Swift contributors, and possibly lower the barrier to getting involved with LLVM.
 
 ### Accepted proposals