Skip to content

Record #70065 in the changelog #70262

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 7, 2023
+14 −0
Merged

Record #70065 in the changelog #70262

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,19 @@
> **Note**\
> This is in reverse chronological order, so newer entries are added to the top.
* [#70065][]:

With the implementation of [SE-0110][], a closure parameter syntax consisting
of only a parameter type — and no parameter name — was accidentally made legal
for certain unambiguous type syntaxes in Swift 4. For example:

```swift
let closure = { ([Int]) in }
```

Having been [gated](https://github.com/apple/swift/pull/28171) behind a
compiler warning since at least Swift 5.2, this syntax is now rejected.

## Swift 5.9.2

* [SE-0407][]:
Expand Down Expand Up @@ -9889,4 +9902,5 @@ using the `.dynamicType` member to retrieve the type of an expression should mig
[#57081]: <https://github.com/apple/swift/issues/57081>
[#57225]: <https://github.com/apple/swift/issues/57225>
[#56139]: <https://github.com/apple/swift/issues/56139>
[#70065]: <https://github.com/apple/swift/pull/70065>
[swift-syntax]: https://github.com/apple/swift-syntax