From 8ae6b791a8171995a87be887ee568e28c1b3ace4 Mon Sep 17 00:00:00 2001 From: Hanton Yang Date: Fri, 18 Nov 2022 21:21:16 -0800 Subject: [PATCH] Fix typo in SE-0156 link --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8c1c71c..4795533 100644 --- a/README.md +++ b/README.md @@ -2114,7 +2114,7 @@ _You can enable the following settings in Xcode by running [this script](resourc #### Why? - [SE-0156](https://github.com/apple/swift-evolution/blob/master/proposals/0156-subclass-existentials.md]), which introduced support for using the `AnyObject` keyword as a protocol constraint, recommends preferring `AnyObject` over `class`: + [SE-0156](https://github.com/apple/swift-evolution/blob/master/proposals/0156-subclass-existentials.md), which introduced support for using the `AnyObject` keyword as a protocol constraint, recommends preferring `AnyObject` over `class`: > This proposal merges the concepts of `class` and `AnyObject`, which now have the same meaning: they represent an existential for classes. To get rid of the duplication, we suggest only keeping `AnyObject` around. To reduce source-breakage to a minimum, `class` could be redefined as `typealias class = AnyObject` and give a deprecation warning on class for the first version of Swift this proposal is implemented in. Later, `class` could be removed in a subsequent version of Swift.