title: bridgeToObjectiveC and makeObjectsPerformSelector in Swift beta 5
body: <p>I had this code with a completion handler working in Xcode 6 beta 4 that no longer works in Xcode 6 beta 5.</p>
  
  <pre><code>dropsToRemove.bridgeToObjectiveC().makeObjectsPerformSelector("removeFromSuperview")
  </code></pre>
  
  <p>Full method...</p>
  
  <pre><code>func animateRemovingDrops(dropsToRemove: [UIView]) {
      println(__FUNCTION__)
      UIView.animateWithDuration(1.0,
          animations: {
              for dropView in dropsToRemove {
                  let x = CGFloat(UInt(arc4random_uniform(UInt32(UInt(self.gameView.bounds.size.width) * 5)))) - self.gameView.bounds.size.width * 2
                  let y = self.gameView.bounds.size.height
                  dropView.center = CGPointMake(x, -y)
          }}, completion: { finished in
                  dropsToRemove.bridgeToObjectiveC().makeObjectsPerformSelector("removeFromSuperview")
          })
  }
  </code></pre>
  
  <p>The error is '[UIView]' does not have a member named 'bridgeToObjectiveC'</p>
  
  <p>Note that the CGFloat and Uint casting in the method is for a beta 4 workaround, I just haven't updated that part yet. That issue is covered at:
  <a href="https://stackoverflow.com/questions/24873219/cgfloat-is-not-convertible-to-uint8-and-other-cgfloat-issues-with-swift-and">‘CGFloat’ is not convertible to ‘UInt8&#39; and other CGFloat issues with Swift and Xcode 6 beta 4</a></p>
  
  <p>I thought the solution for dealing with the completion handler might be to treat the array as an NSArray as detailed in:
  <a href="https://stackoverflow.com/questions/24446372/what-is-the-swift-equivalent-of-makeobjectsperformselector">What is the swift equivalent of makeObjectsPerformSelector?</a></p>
  
  <pre><code>(dropsToRemove as NSArray).makeObjectsPerformSelector("removeFromSuperview")
  </code></pre>
  
  <p>However, assuming I got the syntax right, simply results in another error 'makeObjectsPerformSelector' is unavailable: 'performSelector' methods are unavailable</p>
  
  <p>Is this a new Swift bug, or something I'm missing in the release notes?</p>