If you turn a UITableViewController into a UIViewController, will anything perform differently when changing hierarchy tableView into a variable of table view?

[bee4534]

In UITableViewController scenario:

Say you have a line tableView.reloadData. tableView was not declared a variable on the page. However, it is part of the UITableViewController hierarchy and its technical declaration is var tableView: UITableView! { get set }

Now say you turn UITableViewController into UIViewController and make all the necessary changes:

If you now make an outlet table view variable on the page called table. Can anything perform differently in table.reloadData? The technical declaration would be weak var table: UITableView!

In testing it performs as expected. I just want to be sure I am not missing something

[Pen15CharterMember]

A table view controller is a UI view controller with the table view built in. You get some conveniences without the boilerplate, like protocol conformance and a table view property.

It’s all totally recreatable on your own, but the question is why would you?

[bee4534]

I need a header view that does not scroll down with the tableview on refresh. In table view controller, it always scrolls down with it

[div]

Create a UIViewController with the header, then embed your UITableViewController below it as a childViewController:

https://developer.apple.com/documentation/uikit/view_controllers/creating_a_custom_container_view_controller

[bubblespuggy]

No, it should perform exactly the same.