Скачать или смотреть How to Use a Generic Protocol for Delegates in a Non-Generic Type in Swift?

Discover how to effectively implement a `generic protocol` for delegate properties in Swift without making your class generic. Learn through practical solutions and examples.
---
This video is based on the question https://stackoverflow.com/q/64326148/ asked by the user 'Guig' ( https://stackoverflow.com/u/2054629/ ) and on the answer https://stackoverflow.com/a/64326898/ provided by the user 'Sweeper' ( https://stackoverflow.com/u/5133585/ ) 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: Can I use a generic protocol to describe a delegate in a non generic type?

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.
---
Solving the Delegate Dilemma in Swift: Using a Generic Protocol in a Non-Generic Type

In Swift, managing delegates can become daunting, especially when you want to utilize a generic protocol without transforming your entire class into a generic one. This problem typically arises when you are trying to define a delegate property through a generic protocol which requires associated types. You might encounter errors and complications that can lead to frustration. In this post, we'll address this common issue and provide a clear path towards implementing a solution that retains the flexibility of generics without compromising the structure of your code.

Understanding the Problem

Let’s begin by clarifying the scenario where the issue typically arises. Consider you have a generic protocol called ActionHandler, which requires a type associated with it. Here’s a simplified version of the protocol:

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

You want to use this protocol as a delegate within a non-generic class, like so:

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

However, you might face the following error: "Protocol 'ActionHandler' can only be used as a generic constraint because it has Self or associated type requirements." This indicates that Swift does not allow you to use protocols with associated types directly in this manner.

Alternative Approach: Using Closures

In lieu of making your class generic, a workaround could be to replace the protocol with a closure for handling actions. While this is a feasible approach, it can make your code less elegant and requires additional setup for every method in the protocol that you wish to implement using closures. Below is a closure-based approach you could take:

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

However, the pursuit of simplicity and clarity leads us to a better solution.

A Better Solution: Leveraging a Type Eraser

Instead of overhauling everything by resorting to closures or making Foo generic, we can introduce a type eraser. This mechanism allows us to encapsulate the generic behavior without losing the benefits of type safety. Here’s how you can do it:

Step 1: Create the Type Eraser

Define a class AnyActionHandler which acts as a container for any handler conforming to ActionHandler:

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

Step 2: Implement the Generic Handler in Your Class

Now within your Foo class, redefine your delegate property. Instead of directly using the ActionHandler protocol, utilize the AnyActionHandler as follows:

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

Step 3: Assigning the Handler

Finally, when you create an instance of Foo, you assign your handler like so:

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

This solution allows you to use generic protocols effectively without turning every aspect of your class into a generic type. You maintain type safety and the elegance of the delegate pattern while also simplifying your code structure.

Conclusion

Using a generic protocol for delegates in Swift doesn't have to complicate your class structure. By implementing a type eraser, we can encapsulate the behavior of our generic protocol and seamlessly include it in our non-generic types. This way, we achieve both flexibility and clarity in our code. If you find yourself wrestling with protocols and delegates in Swift, give this approach a try—your code will thank you!