New in Python 3.8: Some of the benefits of interfaces and protocols are type hinting during the development process using tools built into IDEs and static type analysis for detection of errors before runtime. This way, a static analysis tool can tell you when you check your code if you’re trying to access any members … Read more
Protocol inheritance uses the regular inheritance syntax in Swift. protocol Base { func someFunc() } protocol Extended : Base { func anotherFunc() } Swift Protocols do not by default conform to NSObjectProtocol. If you do choose to have your protocol conform to NSObjectProtocol, you will limit your protocol to only being used with classes.
Read up on the State design pattern to learn how to avoid lots of switch statements. “sometimes what comes out has some “blind spot”, I mean statuses of the protocol that have not been covered…” State can help avoid gaps. It can’t guarantee a good design, you still have to do that. “…as I have … Read more
It’s because it’s impossible to conform to a protocol at any access level other than the access level of the protocol itself. In other words, if you have a public protocol, you cannot have private conformance to it. This is partially because protocol conformance is something that can be queried for at runtime (and therefore … Read more
You can review Apple’s Documentation (subsection Method Requirements). There says: As with type property requirements, you always prefix type method requirements with the static keyword when they are defined in a protocol. This is true even though type method requirements are prefixed with the class or static keyword when implemented by a class In practice, … Read more
Protocols can have associatedtypes which would just need to be adhered to in any subclass: enum MyEnum: String { case foo case bar } protocol RequiresEnum { associatedtype SomeEnumType: RawRepresentable where SomeEnumType.RawValue: StringProtocol func doSomethingWithEnum(someEnumType: SomeEnumType) } class MyRequiresEnum: RequiresEnum { typealias SomeEnumType = MyEnum func doSomethingWithEnum(someEnumType: SomeEnumType) { switch someEnumType { case .foo: print(“foo”) … Read more
I ran into the same problem when I tried to implement weak containers. As @plivesey points out in a comment above, this seems to be a bug in Swift 2.2 / Xcode 7.3, but it is expected to work. However, the problem does not occur for some Foundation protocols. For example, this compiles: let container … Read more
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 … Read more
A reason that’s both technical and historical is that text protocols are almost always preferred in the Unix world. Well, this is not really a reason but a pattern. The rationale behind this is that text protocols allows you to see what’s going on on the network by just dumping everything that goes through. You … Read more
As DJ pointed out, TCP is about getting a reliable data stream, and will slow down transmission, and re-transmit corrupted packets, in order to achieve that. UDP does not care about reliability of the communication, and will not slow down or re-transmit data. If your application needs a reliable data stream, for example, to retrieve … Read more