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
Mark `SyntaxArena` and `ParsingSyntaxArena` with `@_spi(RawSyntax)`.
`SyntaxArena` and its subclass `ParsingSyntaxArena` were only meant be
used when dealing with `RawSyntax` which is already a SPI.
Although type type itself was `public`, most initializers were SPI, also
there was no way to retrieve it from existing types via public API. So we
assume no one was actually using it directly.
Copy file name to clipboardExpand all lines: Release Notes/602.md
+6
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,12 @@
14
14
- Migration steps: Replace uses of `ExpandEditorPlaceholdersToTrailingClosures` with `ExpandEditorPlaceholdersToLiteralClosures`. The initializer does not need to change: `.init(indentationWidth:)` on the new type provides the same behavior as the old type.
15
15
- Notes: This improves code completion in a SourceKitLSP session where the trailing closure form may be undesirable. The nested placeholders offer more flexibility to end users, in editors that support it.
16
16
17
+
-`SyntaxArena` and `ParsingSyntaxArena` has changed to SPI
18
+
- Description: `SyntaxArena` and the subclasses were only meant to be used when dealing with `RawSyntax` which is also SPI.
- Migration steps: Do not use `SyntaxArena` or `ParsingSyntaxArena` directly.
21
+
- Notes: Although the type itself was `public`, most initializers were already SPI and there was no way to retrive them from existing types via public API.
0 commit comments