Open Radar

 
Summary:
Due to Swift’s more rigid rules about designated and convenience initializers, the implementation of -[UITableViewController initWithStyle:] is problematic. If I have a subclass of UITableViewController, and I want to define a new designated initializer:

class MyTableVC : UITableViewController {
	let foo: Int
	init(foo: Int) {
		self.foo = foo
		super.init(style: .Grouped)
	}
}

This will build but crash at runtime because MyTableVC doesn’t implement init(nibName:bundle:). However, it shouldn’t have to! If we implement that method, we have a problem with the “foo” property:

class MyTableVC : UITableViewController {
	let foo: Int
	init(foo: Int) {
		self.foo = foo
		super.init(style: .Grouped)
	}
	init(nibName: String!, bundle: String!) {
		// what do we set foo to?
		super.init(nibName: nibName, bundle: bundle)
	}
}

If backwards compatibility is a problem, perhaps a new (truly designated) initializer could be added to UITableViewController for use from Swift subclasses.

Notes:

See some discussion here: https://devforums.apple.com/message/987922