NSIndexPath and IndexPath in Swift 3.0

匿名 (未验证) 提交于 2019-12-03 02:06:01

问题:

I have recently converted my code to Swift 3.0. My collection view and table view data source methods now contain IndexPath instead of NSIndexPath in their method signature. But still inside the method definition it is type casting IndexPath to NSIndexPath. i.e.

func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell     {         let cell : NNAmenitiesOrFurnishingCollectionViewCell = self.amenitiesOrFurnishingCollectionView.dequeueReusableCell(withReuseIdentifier: "NNAmenitiesOrFurnishingCollectionViewCell", for: indexPath) as! NNAmenitiesOrFurnishingCollectionViewCell         cell.facilityImageName = self.facilityArray[(indexPath as NSIndexPath).row].imageName         cell.facilityLabelString = self.facilityArray[(indexPath as NSIndexPath).row].labelText         return cell     } 

Can anyone tell me why indexPath is type casted to NSIndexPath.

回答1:

There is no reason to cast IndexPath to NSIndexPath here. The Swift 3 overlay type IndexPath has properties

/// The section of this index path, when used with `UITableView`. /// /// - precondition: The index path must have exactly two elements. public var section: Int  /// The row of this index path, when used with `UITableView`. /// /// - precondition: The index path must have exactly two elements. public var row: Int 

which you can access directly:

    cell.facilityImageName = self.facilityArray[indexPath.row].imageName     cell.facilityLabelString = self.facilityArray[indexPath.row].labelText 

Apparently the Xcode migrator did not a perfect job.



标签
易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!