What is Protocol Oriented Programming in Swift? What added value does it bring?

Question

From Apple's own website: "At the heart of Swift's design are two incredibly powerful ideas: protocol-oriented programming and first class value semantics."

Can someone please elaborate what exactly is protocol oriented programming, and what added value does it bring?

I have read this and watched the Protocol-Oriented Programming in Swift video, but coming from an Objective-C background still haven't understood it. I kindly ask for a very plain English answer along with code snippets & technical details about how it's different from Objective-C.

Just one of the confusions I have is using <tableViewDelegate, CustomDelegate> Couldn't we also conform to multiple protocols in Objective-C as well? So again how is Swift new?

---

EDIT: See Protocol-Oriented Views video. I find this video to be more basic and easier to grasp a meaningful use case. The WWDC video itself is a bit advanced and requires more breadth. Additionally the answers here are somewhat abstract.

Answer 1

what is protocol oriented programming? What’s POP?

• is a new programming paradigm

• we start designing our system by defining protocols. We rely on new concepts: protocol extensions, protocol inheritance, and protocol compositions.

• value types can inherit from protocols, even multiple protocols. Thus, with POP, value types have become first class citizens in Swift. value types like enums, structs *POP lets you to add abilities to a class or struct or enum with protocols which supports multiple implementations.

• Apple tells us: “Don’t start with a class, start with a protocol.” Why? Protocols serve as better abstractions than classes.

Protocols: are a fundamental feature of Swift. They play a leading role in the structure of the Swift standard library and are a common method of abstraction. Protocols are used to define a “blueprint of methods, properties, and other requirements that suit a particular task or piece of functionality.”

Benefits of Protocol-Oriented Programming:

• All classes are decoupled from each other
• Separating the concerns of declaration from implementation
• Reusability
• Testability

Answer 2

Protocol Oriented Programming(POP)

protocol-first approach

• Protocol as a key point of OOP concept. abstraction, inheritance, polymorphism, encapsulation.
• Protocol as a base for SOLID^[About]
• Protocol instead of class hierarchy tree. Its is hard to support class inheritance. Moreover it has some performance impact
• Class/struct can implements multiple protocols(a kind of multiple inheritance)
• Composition over inheritance.

extension MyClass: MyProtocol {
}

• Default method. Shared implementation for all implementators

extension MyProtocol {
    func foo() {
        //logic
    }
}

• Protocol inheritance. One protocol can extends another protocol. Implementator of protocol one should implements all from first and the second protocols

protocol ProtocolB: ProtocolA {
}

• value type implement protocol(as usual reference type)^[About]

Answer 3

Protocol Oriented Programming (POP)

• Came since Swift 2.0
• class (OOP)
  • is reference type
  • memory leak, incorrect data stored,race condition to access in complex multi-thread environments
  • can be large by inheriting members of super classes at chain time
• struct (POP)
  • is value type - each time a fresh copy is made when needed
  • provides multi inheritance - inherits protocols
  • Protocol :
  • Defines what Methods, Properties and Initializes are required o Can inherit another Protocol(s)
  • Don’t have to use override keyword to implement protocol functions
• Extensions:
  • Default value and The default implementation for protocol
  • Can add extra members to protocol

Answer 4

It surprised me that none of the answers mentioned value type in POP.

To understand what is protocol oriented programming, you need to understand what are drawbacks of objected oriented programming.

1. It (Objc) has only one inheritance. If we have very complicated hierarchy of inheritance, the bottom class may have a lot of unnecessary state to hold.
2. It uses class which is a reference type. Reference type may cause code unsafe. e.g. Processing collection of reference types while they are being modified.

While in protocol oriented programming in swift:

1. It can conform multiple protocols.
2. It can be used by not only class, but also structures and enumerations.
3. It has protocol extension which gives us common functionality to all types that conforms to a protocol.
4. It prefers to use value type instead of reference type. Have a look at the standard swift library here, you can find majority of types are structures which is value type. But this doesn't mean you don't use class at all, in some situation, you have to use class.

So protocol oriented programming is nothing but just an another programming paradigm that try to solve the OOP drawbacks.

Answer 5

Adding to the above answer

Protocol is a interface in which signature of methods and properties are declared and any class/struct/enum subclassing the enum must have to obey the contract means they have to implement all the methods and properties declared in superclass protocol.

Reason to use Protocol

Classes provide single inheritance and struct doesn't support inheritance. Thus protocols was introduced.

Extension The methods declare inside the protocol can be implemented inside the extension to avoid the redundancy of the code in case protocol is being inherited in multiple class / struct having same method implementation. We can call the method by simply declaring the object of struct/enums. Even we can restrict the extension to a list of classes, only restricted class will be able to use the method implemented inside the extension while rest of the classes have to implement method inside own class.

Example

protocol validator{

    var id : String{ get }
    func capitialise()-> (String)

}

extension validator where Self : test{
    func capitialise() -> String{
        return id.capitalized
    }
}

class test : validator {

    var id: String

    init(name:String) {
        id = name
    }
}

let t = test(name: "Ankit")
t.capitialise()

When to use In OOP suppose we have a vehicle base class which is inherited by the airplane, bike, car etc. Here break, acceleration may be common method among three subclass but not the flyable method of airplane. Thus if we are declaring flyable method also in OOP, the bike and car subclass also have the inherit flyable method which is of no use for those class. Thus in the POP we can declare two protocols one is for flyable objects and other is for break and acceleration methods. And flyable protocol can be restricted to use by only the airplane

Answer 6

In Objective C protocol is the same thing as interface in most languages. So in Objective C protocol's usage is limited to SOLID principle "Depend upon Abstractions. Do not depend upon concretions."

In Swift protocols were improved so seriously that since they still could be used as interfaces in fact they are closer to classes (like Abstract classes in C++)

In Objective C the only way to share functionality between classes is an inheritance. And you could inherit the only one parent class. In Swift you could also adopt as many protocols as you want. And since protocols in Swift can have default methods implementation they give us a fully-functional Multiple inheritance. More flexibility, better code reuse - awesome!

Conclusion:

Protocol Oriented Programming is mostly the same as OOP but it pays additional attention to functionality sharing not only via inheritance but also via protocol adoption (Composition over inheritance).

Worth to mention that in C++ abstract classes are very similar to protocols in Swift but no one says C++ supports some specific type of OOP. So in general POP is a one of the versions of OOP if we speak about programming paradigms. For Swift POP is an improved version of OOP.

Answer 7

Preface: POP and OOP are not mutually exclusive. They're design paradigms that are greatly related.

The primary aspect of POP over OOP is that is prefers composition over inheritance. There are several benefits to this.

In large inheritance hierarchies, the ancestor classes tend to contain most of the (generalized) functionality, with the leaf subclasses making only minimal contributions. The issue here is that the ancestor classes end up doing a lot of things. For example, a Car drives, stores cargo, seats passengers, plays music, etc. These are many functionalities that are each quite distinct, but they all get indivisibly lumped into the Car class. Descendants of Car, such as Ferrari, Toyota, BMW, etc. all make minimal modifications to this base class.

The consequence of this is that there is reduced code reuse. My BoomBox also plays music, but it's not a car. Inheriting the music-playing functionality from Car isn't possible.

What Swift encourages instead is that these large monolithic classes be broken down into a composition of smaller components. These components can then be more easily reused. Both Car and BoomBox can use MusicPlayer.

Swift offers multiple features to achieve this, but the most important by far are protocol extensions. They allow implementation of a protocol to exist separate of its implementing class, so that many classes may simply implement this protocol and instantly gain its functionality.