You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2-4Lines changed: 2 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,13 @@
2
2
3
3
_**Note:** This is in reverse chronological order, so newer entries are added to the top._
4
4
5
-
## Swift 6.0
5
+
## Swift 5.8
6
6
7
7
*[SE-0365][]:
8
8
9
9
Implicit `self` is now permitted for `weak self` captures, after `self` is unwrapped.
10
10
11
-
For example, the usage of implicit `self` below is now permitted:
11
+
For example, the usage of implicit `self` below is permitted:
12
12
13
13
```swift
14
14
classViewController {
@@ -44,8 +44,6 @@ _**Note:** This is in reverse chronological order, so newer entries are added to
44
44
45
45
In Swift 6, the above code will no longer compile. `weak self` captures in non-escaping closures now have the same behavior as captures in escaping closures (as described in [SE-0365][]). Code relying on the previous behavior will need to be updated to either unwrap `self` (e.g. by adding a `guard let self else return` statement), or to use a different capture method (e.g. using `[self]` or `[unowned self]` instead of `[weak self]`).
46
46
47
-
## Swift 5.8
48
-
49
47
*[SE-0362][]:
50
48
51
49
The compiler flag `-enable-upcoming-feature X` can now be used to enable a specific feature `X` that has been accepted by the evolution process, but whose introduction into the language is waiting for the next major version (e.g., version 6). The `X` is specified by any proposal that falls into this category:
0 commit comments