title: code involving indexPath & NSIndexPath works - but why is it redundant?
body: <p>I'm getting back to using CloudKit and in the project I'm revisiting, I have a query fetch performed and I am left with an array of CKRecords. I'm setting this array to be displayed via TableController.  Anyways, I have this one line of code (which works)... but I am just unsure why I am setting the indexPath as NSIndexPath.  </p>
  
  <pre><code> override func tableView(_ tableView: UITableView, cellForRowAt indexPath: IndexPath) -&gt; UITableViewCell {
      let cell = tableView.dequeueReusableCell(withIdentifier: "dining") as! table1cell
      let restaurant: CKRecord = categories[(indexPath as NSIndexPath).row]
      cell.Name.text = restaurant.value(forKey: "Name") as? String
  
      return cell
  </code></pre>
  
  <p>With my other non-CKRecord TableController projects, I know I don't have to set the indexPath to itself, in essence.  What am I missing here? </p>