Скачать или смотреть Extending a Swift Protocol: Making Your Classes Work Smarter with isSharable

Learn how to effectively extend Swift protocols with extensions, enabling classes to inherit implemented variables like `isSharable`, without additional coding.
---
This video is based on the question https://stackoverflow.com/q/67401067/ asked by the user 'WalterBeiter' ( https://stackoverflow.com/u/5769930/ ) and on the answer https://stackoverflow.com/a/67401327/ provided by the user 'Andrew' ( https://stackoverflow.com/u/5508175/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: how to extend a swift protocol with an extension so that classes get an implemented variable defined by the protocol

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Extending a Swift Protocol: Enabling Your Classes to Inherit isSharable

In the world of Swift programming, protocols and extensions are powerful tools that can help you write cleaner, more efficient code. However, one common challenge is figuring out how to extend a protocol so that implementing classes can seamlessly inherit certain properties or functionalities without unnecessary complexity. In this guide, we will explore how to extend a Swift protocol with an implementation so that subclasses can adopt variables defined by the protocol, using the example of a User class and a Sharable protocol.

The Problem

Let's start by introducing our User class:

[[See Video to Reveal this Text or Code Snippet]]

We also have a protocol Sharable defined as follows:

[[See Video to Reveal this Text or Code Snippet]]

The main intention is to extend the Sharable protocol in such a way that the subclasses of User can automatically adopt an implemented version of share(name:) and have access to the isSharable variable.

However, if we try to implement this using the following extension:

[[See Video to Reveal this Text or Code Snippet]]

And then create a subclass Admin like this:

[[See Video to Reveal this Text or Code Snippet]]

Xcode will show an error indicating that 'Admin' does not conform to protocol 'Sharable'. This happens because the requirement for isSharable is not satisfied by our extension, leading to confusion and additional setup that we want to avoid.

Understanding the Confusion

The reason for the error lies in how isSharable is defined in your protocol as { get set }. This means that any conforming class must provide both a getter and a setter for isSharable. Since our extension only provides a computed property (which is inherently read-only), it does not conform to the protocol as required.

To resolve this issue, let's make a key change.

The Solution

To allow your subclasses to enjoy this functionality with less boilerplate code, you should modify the Sharable protocol by removing the set requirement from isSharable. This will make it a read-only property:

[[See Video to Reveal this Text or Code Snippet]]

With this change, isSharable becomes a computed property that only requires a getter, which can be implemented in the extension. Therefore, your extension now looks like this:

[[See Video to Reveal this Text or Code Snippet]]

Now, when you create the Admin class like this:

[[See Video to Reveal this Text or Code Snippet]]

It will have access to the functionality you defined in the protocol's extension without needing to override or define isSharable or share functions manually. This means the setup is much cleaner, and you achieve the desired functionality effortlessly.

Sample Usage

Once everything is set up, you can use your Admin class freely, as shown below:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By adjusting the protocol definition from { get set } to { get }, we've enabled subclasses to inherit shared functionalities without additional complexities. This not only simplifies the implementation but also promotes reusable and maintainable code. So, go ahead and explore the ways Swift's protocols can help you write cleaner code while managing shared functionalities effectively!