You just have to invert the order super.init/properties in your initializer:
required init(coder aDecoder: NSCoder) {
self.datasourceOfflineVideos = ASDataSource(tableViewController: self)
self.datasourceOnlineVideos = ASDataSource(tableViewController: self)
super.init(coder: aDecoder)
}
instance properties comes first, then the superclass initializer can be invoked. But that's not possible in your case, because you are referencing self
.
The workaround in this case is to make the properties implicitly unwrapped optionals:
var datasourceOnlineVideos:ASDataSource!
var datasourceOfflineVideos:ASDataSource!
Since optionals don't need to be initialized, you can safely initialize them after the super.init
method has been called. Being implicitly unwrapped, you use them as any other non optional property.
This pattern is used by Apple in several classes, including UIViewController
: when you add an outlet from IB, the component property is always declared as implicitly unwrapped. That's because the control itself is not instantiated in the initializer, but at a later stage.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…