Frank Schmitt Frank Schmitt - 3 days ago 6
Swift Question

How do I declare a variable that has a type and implements a protocol?

My app has a protocol for detail view controllers, stating they must have a

viewModel
property:

protocol DetailViewController: class {
var viewModel: ViewModel? {get set}
}


I also have a few different classes that implement the protocol:

class FormViewController: UITableViewController, DetailViewController {
// ...
}

class MapViewController: UIViewController, DetailViewController {
// ...
}


My master view controller needs a property that can be set to any
UIViewController
subclass that implements the
DetailViewController
protocol.

Unfortunately I can't find any documentation on how to do this. In Objective-C it would be trivial:

@property (strong, nonatomic) UIViewController<DetailViewController>;


It appears that there isn't any syntax available in Swift to do this. The closest I've come is to declare a generic in my class definition:

class MasterViewController<T where T:UIViewController, T:DetailViewController>: UITableViewController {
var detailViewController: T?
// ...
}


But then I get an error saying that "Class 'MasterViewController' does not implement its superclass's required members"

This seems like it should be as easy to do in Swift as it is in Objective-C, but I can't find anything anywhere that suggests how I might go about it.

Answer

I think you can get there by adding an (empty) extension to UIViewController and then specifying your detailViewController attribute using a composed protocol of the empty extension and your DetailViewController. Like this:

protocol UIViewControllerInject {}
extension UIViewController : UIViewControllerInject {}

Now all subclasses of UIViewController satisfy protocol UIViewControllerInject. Then with that, simply:

typealias DetailViewControllerComposed = protocol<DetailViewController, UIViewControllerInject>

class MasterViewController : UITableViewController {
  var detailViewController : DetailViewControllerComposed?
  // ...
}

But, this is not particularly 'natural'.

=== Edit, Addition ===

Actually, you could make it a bit better if you define your DetailViewController using my suggested UIViewControllerInject. Like such:

protocol UIViewControllerInject {}
extension UIViewController : UIViewControllerInject {}

protocol DetailViewController : UIViewControllerInject { /* ... */ }

and now you don't need to explicitly compose something (my DetailViewControllerComposed) and can use DetailViewController? as the type for detailViewController.

Comments