CODEWITHSUNDEEP
iosswiftsyntaxprotocols
Clay Ellis
Clay Ellis

Reputation: 5330

Swift Protocol - Property type subclass

I'm defining a protocol called PanelController in which I'd like to store a PanelView. PanelView itself is a subclass of UIView and defines the basic structure of panel. I have three different views that subclass PanelView: LeftPanel, MidPanel, and RightPanel. For each of those panels I'd like to define a xxxPanelController (left, mid, right) that conforms to the PanelController protocol.

The issue I'm running up against is in the protocol and xxxPanelController

protocol PanelController {
    var panelView: PanelView { get set }
    ...
}

and

class LeftPanelController: UIViewController, PanelController {
    var panelView = LeftPanelView()
    ...
}

where

class LeftPanelView: PanelView {
     ...
}

and (one last piece...)

class PanelView: UIView {
    ...
}

I get an error saying that: LeftPanelController does not conform to protocol PanelController for an obvious reason: panelView is of type LeftPanelView not PanelView. This seems really limited to me, though, because LeftPanelView is a subclass of PanelView so it should just work! But it doesn't!

Can someone explain to me why this is, and if anyone can come up with one, a possible workaround? Thanks!

Upvotes: 20

Views: 2796

Answers (1)

Eric
Eric

Reputation: 2097

The problem is with the setter in the protocol.

Let's say you want to GET the panelView from LeftPanelController. That's fine, because LeftPanelView can do everything PanelView can do (and more).

If you want to SET the panelView of LeftPanelController though, you can give it any PanelView. Because you're defining the panelView variable as a LeftPanelView, the setter could sometimes fail.

To fix this, you could do the following in LeftPanelController:

var panelView: PanelView = LeftPanelView()

The implication of this is that you won't be able to access any methods or properties that are specific to LeftPanelView without casting it first. If that's not an issue, then this should fix your problem!

Upvotes: 11

Related Questions