Skip to content

Commit 3589903

Browse files
committed
Remove some whitespaces
1 parent 1567f9f commit 3589903

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Release Notes/600.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@
124124
- Description: Types can have multiple specifiers now and the syntax tree has been modified to reflect that.
125125
- Pull request: https://github.com/apple/swift-syntax/pull/2433
126126

127-
- ` CanImportExprSyntax` and `CanImportVersionInfoSyntax`
127+
- `CanImportExprSyntax` and `CanImportVersionInfoSyntax`
128128
- Description: Instead of parsing `canImport` inside `#if` directives as a special expression node, parse it as a functionc call expression. This is in-line with how the `swift(>=6.0)` and `compiler(>=6.0)` directives are parsed.
129129
- Pull request: https://github.com/apple/swift-syntax/pull/2025
130130

@@ -137,7 +137,7 @@
137137
- Pull request: https://github.com/apple/swift-syntax/pull/2587
138138

139139
- `ByteSourceRange` deprecated in favor of `Range<AbsolutePosition>`
140-
- Description: `ByteSourceRange` is being dropped for `Range<AbsolutePosition>`, where the latter clearly signifies that it uses UTF-8 byte positions. `Range<AbsolutePosition>` has deprecated compatibility layers to make it API-compatible with `ByteSourceRange`
140+
- Description: `ByteSourceRange` is being dropped for `Range<AbsolutePosition>`, where the latter clearly signifies that it uses UTF-8 byte positions. `Range<AbsolutePosition>` has deprecated compatibility layers to make it API-compatible with `ByteSourceRange`
141141
- Pull request: https://github.com/apple/swift-syntax/pull/2587
142142

143143
## API-Incompatible Changes

0 commit comments

Comments
 (0)