## Summary In [SE-0458](https://github.com/swiftlang/swift-evolution/blob/main/proposals/0458-strict-memory-safety.md), the new `unsafe` expression has been added. However, swift-format still can't handle it correctly. ## Prerequisites - swift-format main branch 88a8900f4fd7902367261756575fdd0039e8aa58 - swift-syntax main branch [94681bad0aa2ef3a277d2895e7f0c9e60ec2bbb1](https://github.com/swiftlang/swift-syntax/commit/94681bad0aa2ef3a277d2895e7f0c9e60ec2bbb1) ## Steps to reproduce 1. Create `test.swift` ```swift _ = unsafe UnsafeRawPointer(bitPattern: 0) ``` 2. Run `swift-format format test.swift` ## Expected output ```swift _ = unsafe UnsafeRawPointer(bitPattern: 0) ``` ## Actual output It breaks the source code. ```swift _ = unsafeUnsafeRawPointer(bitPattern: 0) ```