A “Type Erasure” Pattern that Works in Swift:类型域的转换
新视角:通过函数式编程的范畴理论来看待这个问题会更容易理解;
在低层类型无法很好表达的类型,可以将其转化为高阶类型进行表示。
将协议的实现类型转化为monad类型;
解决将具有关联类型的协议当作类型的
swift所谓的类型擦除是指通过协议的泛型化、继承、封装,将协议类型抹除的过程;
泛化的最终目的:
将实现了同一协议,并且关联类型一样的类型作为同一类型来看待。
接口类型最终目的:
1、接口类型用实例类型初始化后的行为和实例类型的行为一致;
2、实现了协议的可类型化,和实例类型的封装;
3、隐藏了底层的实现细节,合并了类型功能和封装功能;
let testGo: [_AnyCupBase<Coffee>] = [_AnyCupBox(CoffeeMug()), _AnyCupBox(CoffeeCup())]
终极限制:关联类型的一致性必须的到满足;
涉及到的元素:
关联类型的可指定类型;
协议的实例类型;
协议的泛化类型:协议的可类型化;用于做类型使用;用于确保关联类型的一致性;用于将容器类型从关联类型的功能中解放出来
容器类型、泛化类型的继承:1、用于包装协议的实例类型;2、用于给协议的泛化类型指定类型;
接口类型:1、接口层面只包含泛型化的关联类型;2、将协议的泛化类型作为类型来引用容器类型;3、初始化容器类型,赋值给协议的泛化类型类型;
协议的泛化是协议可类型化的基础;
消息的传递通过类似与代理机转发机制来实现。
Introduction
If you have ever tried to use Swift protocols with associated types as types, you probably had (just like me) a very rough first (and possibly second) ride. Things that should be intuitively doable are just not and the compiler gives infuriating error messages. It comes down to the fact that the language is not yet “finished” (and, as a result, protocols are not really usable as types — yet). The good news is that problems have workarounds and one such workaround is “type erasure” (not the Java compiler feature, something else that goes by the same name). Apple uses the type erasure pattern every time you read Any<Something> and cleverer people than myself described it well (more information in the references at the end). This is my attempt at understanding the pattern.
So what’s the problem?
Imagine that you have a protocol Cup that describes a generic cup, with an associated type Content that describes the cup’s content. Imagine that this protocol has some methods and some properties. For fun (and for realism) let’s make these methods mutating and returning and instance of Self (the specific instance of Cup we are dealing with).
1
2
3
4
5
6
7
8
|
protocol Cup {
// Have an associated type
associatedtype Content
var description: String { get }
// Use this associated type
mutating func replaceContent(with newContent: Content) -> Self
func showContent() -> Content?
}
|
Let’s define some concrete types for Content .
1
2
3
4
5
6
7
8
9
|
struct Tea {
let description = "tea"
let hasMilk: Bool
}
struct Coffee {
let description = "coffee"
let isDecaf: Bool
}
|
Let’s also add some concrete types for the protocol Cup . A cup of tea and a cup of coffee perhaps. Honouring the spirit of Swift, I’ll make them value types ( struct ) but it would work in the same way for a class , without any further adjustment.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
struct TeaMug: Cup {
// Assign a concrete type to the associated type as your first action. This is not necessary but will unleash the power of autocomplete.
typealias Content = Tea
let description = "tea mug"
private var content: Tea?
// Please note that after specialising Content, these lines will autocomplete nicely
mutating func replaceContent(with newContent: Tea) -> TeaMug {
content = newContent
return self
}
func showContent() -> Tea? {
return content
}
}
struct CoffeeMug: Cup {
typealias Content = Coffee
let description = "coffee mug"
private var content: Coffee?
mutating func replaceContent(with newContent: Coffee) -> CoffeeMug {
content = newContent
return self
}
func showContent() -> Coffee? {
return content
}
}
struct CoffeeCup: Cup {
typealias Content = Coffee
let description = "coffee cup"
private var content: Coffee?
mutating func replaceContent(with newContent: Coffee) -> CoffeeCup {
content = newContent
return self
}
func showContent() -> Coffee? {
return content
}
}
|
We can nicely create different instances of cups with different contents.
1
2
3
4
5
|
var myCoffeeCup = CoffeeCup()
myCoffeeCup.replaceContent(with: Coffee(isDecaf: false))
var myTeaMug = TeaMug()
myTeaMug.replaceContent(with: Tea(hasMilk: true))
|
And here are the problems that I invariably face when I start thinking of Cup as a type (it’s not a type! It’s a protocol!).
(1) Collection of protocol types
1
2
3
4
|
let cupboardOne: [Cup] = [CoffeeMug(), CoffeeCup()]
let cupboardTwo: [Cup] = [TeaMug(), TeaMug()]
// The following works but it's probably not what you want, the type is not generic and is a concrete [TeaMug] rather than a generic [Cup]
let cupboardThree = [TeaMug(), TeaMug()]
|
(2) Returning a protocol type in a function
1
2
3
|
func giveMeACup() -> Cup? {
return cupboardOne.first
}
|
(3) Taking a protocol type as a parameter to a function
1
2
3
|
func describe(cup: Cup) {
print(cup.description)
}
|
(4) Using a protocol type as a type for class or struct properties
1
2
3
|
class mySuperDuperClass {
var cup: Cup
}
|
The error message
The error message, in all cases above, is always the same: protocol ‘Cup’ can only be used as a generic constraint because it has Self or associated type requirements. In other words, if a protocol has associated types you cannot use such protocol as a type. It makes sense, the Swift compiler will not know what exact protocol type you are dealing with unless the associated type is specified. A nice mnemonic way to put could be:
Swift does not like multidimensional type uncertainty, but one dimensional type uncertainty is OK.
If we can somehow fix the associated type Content , we can make it work. There are individual workarounds that work for problems (2) to (4) but they have different limitations: we are not going to discuss them here. We are going to present a more general solution that takes care of all four problems.
The Solution
The architecture for the solution requires a few steps and a lot of patience to follow. I will try my best to be clear. Here we go.
(1) Base class mocking the protocol
First let’s define a base class that describes the protocol Cup . The associated type Content is now turned into a generic parameter for the class. The class cannot be used directly because it cannot be initialised. Furthermore, every property and every method throw a fatal error upon access or call: they must be overridden, all of them. Why do we need this base class? It’s a trick. As we will see later, we need to be able to store a subclass of it but we cannot refer directly to an instance of such subclass.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
private class _AnyCupBase<Content>: Cup {
// All the properties in the Cup protocol go here.
var description: String {
get { fatalError("Must override") }
}
// Let's make sure that init() cannot be called to initialise this class.
init() {
guard type(of: self) != _AnyCupBase.self else {
fatalError("Cannot initialise, must subclass")
}
}
// All the methods in the Cup protocol here
func replaceContent(with newContent: Content) -> Self {
fatalError("Must override")
}
func showContent() -> Content? {
fatalError("Must override")
}
}
|
(2) A box containing a concrete instance of the protocol
Let’s define a box, where the concrete type for protocol Cup is stored: such box will inherit from our previously define abstract class. By inheriting from _AnyBase , it also follows the Cup protocol. The generic parameter ConcreteCup also follows the protocol Cup . All methods and properties of ConcreteCup are wrapped by this class. Note that when referring to this class we need to specify a concrete type for Cup . For example: _AnyCupBox<TeaCup> . That is not what we want. When referring to its super class instead, we only need to specify a concrete type for its Content . For example: _AnyCupBase<Tea> . This should shed some light on why we need a base abstract class to inherit from and this trick lays at the heart of the technique.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
|
private final class _AnyCupBox<ConcreteCup: Cup>: _AnyCupBase<ConcreteCup.Content> {
// Store the concrete type
var concrete: ConcreteCup
// Override all properties
override var description: String {
get { return concrete.description }
}
// Define init()
init(_ concrete: ConcreteCup) {
self.concrete = concrete
}
// Override all methods
override func replaceContent(with newContent: ConcreteCup.Content) -> Self {
concrete.replaceContent(with: newContent)
return self
}
override func showContent() -> ConcreteCup.Content? {
return concrete.showContent()
}
}
|
(3) The pseudo-protocol
And finally we can define the public class that we are going to use.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
|
final class AnyCup<Content>: Cup {
// Store the box specialised by content.
// This line is the reason why we need an abstract class _AnyCupBase. We cannot store here an instance of _AnyCupBox directly because the concrete type for Cup is provided by the initialiser, at a later stage.
private let box: _AnyCupBase<Content>
// All properties for the protocol Cup call the equivalent Box proerty
var description: String {
get { return box.description }
}
// Initialise the class with a concrete type of Cup where the content is restricted to be the same as the genric paramenter
init<Concrete: Cup>(_ concrete: Concrete) where Concrete.Content == Content {
box = _AnyCupBox(concrete)
}
// All methods for the protocol Cup just call the e quivalent box method
func replaceContent(with newContent: Content) -> Self {
box.replaceContent(with: newContent)
return self
}
func showContent() -> Content? {
return box.showContent()
}
}
|
See how this works!
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
// Use the generic type in a collection
let cupboardOne: [AnyCup<Coffee>] = [AnyCup(CoffeeMug()), AnyCup(CoffeeCup())]
let cupboardTwo: [AnyCup<Tea>] = [AnyCup(TeaMug()), AnyCup(TeaMug())]
// Return the generic type in a function (explicitely or implicitely)
func giveMeACupOfCoffee() -> AnyCup<Coffee>? {
return cupboardOne.first
}
// Use the generic type as an input to a function
func describe(cup: AnyCup<Coffee>) {
print(cup.description)
}
// Store a generic property
struct myShelf<Content> {
var cup: AnyCup<Content>
}
|
Conclusion
While I am still not very comfortable with this pattern (a lot of boilerplate, difficult to fully grasp), I will give it a go as it seems very general. You can also refer to two other excellent blog posts by Realm and by The Big Nerd Ranch basically outlining the same architecture and source of inspiration for this writing.
https://blog.jayway.com/2017/05/12/a-type-erasure-pattern-that-works-in-swift/
A “Type Erasure” Pattern that Works in Swift:类型域的转换的更多相关文章
- Breaking Down Type Erasure in Swift
Type Erasure Pattern We can use the type erasure pattern to combine both generic type parameters and ...
- 关于type erasure
哇,好久没有写blog了,再不写的话,blog的秘密都要忘记了,嘿嘿. 最近在试着参与一个开源项目,名字叫avim(A Vibrate IM),别想多了哟.地址是:https://github.com ...
- Java魔法堂:解读基于Type Erasure的泛型
一.前言 还记得JDK1.4时遍历列表的辛酸吗?我可是记忆犹新啊,那时因项目需求我从C#转身到Java的怀抱,然后因JDK1.4少了泛型这样语法糖(还有自动装箱.拆箱),让我受尽苦头啊,不过也反映自己 ...
- java,swift,oc互相转换,html5 web开发跨平台
java,swift,oc互相转换,html5 web开发跨平台 写一个java->swift的程序,这个程序是做跨平台系统的核心部分swift和oc到java也在考虑之列Swift->J ...
- Type Erasure with Pokemon---swift的类型擦除
我感觉这个是swift的设计缺陷. 类型擦除:解决泛型类型作为公用类型的问题 是抽象的公用机制的一种实现方式. 1)类型擦除并不能解决类型不一致的兼容问题,只能解决类似继承一致性的兼容问题. 2)擦除 ...
- [ios][swift]Swift类型之间转换
http://www.ruanman.net/swift/learn/4741.html
- Swift中如何转换不同类型的Mutable指针
在Swift中我们拥有强大高级逻辑抽象能力的同时,低级底层操作被刻意的限制了.但是有些情况下我们仍然想做一些在C语言中的hack工作,下面本猫就带大家看一看如何做这样的事. hacking is ha ...
- [Swift]LeetCode756. 金字塔转换矩阵 | Pyramid Transition Matrix
We are stacking blocks to form a pyramid. Each block has a color which is a one letter string, like ...
- [Swift]字符串大小写转换,同时实现本地化或设置语言环境
在NSString中提供了3种字符串大小写转换方式:1. 转换字符串大小写2. 转换字符串大小写,并实现本地化3. 转换字符串大小写,并设置语言环境. 一. 转换字符串大小写如果只是想单纯的将字符串进 ...
随机推荐
- EWS 通过SubscribeToPullNotifications订阅Exchange删除邮件
摘要 在使用拉通知的方式监听exchange邮件的时候,无法监听到收件箱删除的邮件.最后通过调试发现,在删除收件箱邮件的时候,是将收件箱的邮件移动到了deleted item文件夹,会触发Moved事 ...
- 【转载】Nginx+Tomcat 动静分离实现负载均衡
0.前期准备 使用Debian环境.安装Nginx(默认安装),一个web项目,安装tomcat(默认安装)等. 1.一份Nginx.conf配置文件 1 # 定义Nginx运行的用户 和 用户组 如 ...
- Substrings(hdu1238)字符串匹配
Substrings Time Limit: 2000/1000 MS (Java/Others) Memory Limit: 65536/32768 K (Java/Others)Total Sub ...
- Fragment的坑
http://www.jianshu.com/p/d9143a92ad94 使用add()加入fragment时将触发onAttach(),使用attach()不会触发onAttach() 使用rep ...
- macbook 外接显示器黑屏,不显示
我的mac本有点老了,11年底的那款 整了个显示器,刚开始连上没问题,后来开机状态拔了雷电线,再插 或者关机后莫名的原因再启动,显示器黑屏 网上好多方法都不行,自己总结了一个方法 拔掉连接线,关闭m ...
- 【 js 基础 】【读书笔记】Javascript “继承”
是时候写一写 “继承”了,为什么加引号,因为当你阅读完这篇文章,你会知道,说是 继承 其实是不准确的. 一.类1.传统的面向类的语言中的类:类/继承 描述了一种代码的组织结构形式.举个例子:“汽车”可 ...
- 获取url地址的参数值
使用频率很高,百度了记录一下 $.getUrlParam = function (name) { var reg = new RegExp("(^|&)" + name + ...
- element-ui Pagination组件源码分析整理笔记(七)
element-ui源码的版本是2.4.9 pagination.js import Pager from './pager.vue'; import ElSelect from 'element-u ...
- 使用标准C读取文件遇到的结构体对齐问题及其解决办法
作者:朱金灿 来源:http://blog.csdn.net/clever101 同事使用标准C库读取文件,发现总是读取不对,让我帮忙看一下. 原来他定义了如下一个结构体: // 定义块的结构 typ ...
- Hibernate 中配置属性详解(hibernate.properties)
Hibernate能在各种不同环境下工作而设计的, 因此存在着大量的配置参数.多数配置参数都 有比较直观的默认值, 并有随 Hibernate一同分发的配置样例hibernate.properties ...