Worth mentioning that @objc protocols do conform to themselves as long as they
do not have static methods or initializer requirements. However this may be too
heavy-handed if a simple overload can do the trick.
Slava
> On Mar 9, 2017, at 1:10 PM, Guillaume Lessard via swift-users
> wrote:
>
> On Mar 9, 2017, at 12:46, Edward Connell via swift-users
> wrote:
>
> // Everything compiles fine until this
> someFunc(items: items)
This is a frequent pain point: protocol existentials cannot stand in for the
protocol they represent.
Your function wants a concrete type that conforms to It
The error says ItemProtocol does not conform to ItemProtocol.
That doesn't make sense. It seems this should work fine.
// It's all clean until the last line
protocol ItemProtocol : class {
var message: String { get }
}
// heterogenious types
class A : ItemProtocol {
var message = "A"
}
class B :
