Update dependency apple/swift-syntax to v510 - autoclosed #84
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/apple-swift-syntax-510.x
branch
from
b283f6b to
828cc60
Compare
renovate
bot
force-pushed
the
renovate/apple-swift-syntax-510.x
branch
from
828cc60 to
0d9c186
Compare
renovate
bot
force-pushed
the
renovate/apple-swift-syntax-510.x
branch
from
0d9c186 to
47c3d80
Compare
renovate
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
from: "509.0.2"->from: "510.0.3"Release Notes
apple/swift-syntax (apple/swift-syntax)
v510.0.3Compare Source
Compared to 510.0.2 improves swift-syntax’s ability to build using Bazel.
It also contains the following changes from 510.0.0.
New APIs
SyntaxStringInterpolation.appendInterpolation(_: (some SyntaxProtocol)?)nil, nothing will get added to the string interpolation.SyntaxCollection.index(at:)SyntaxCollection. This computation is in O(n) andSyntaxCollectionis not subscriptable by an integer.Convenience initializer
ClosureCaptureSyntax.init()ClosureCaptureSyntaxthat takes a concretenameargument and automatically addsequal = TokenSyntax.equalToken()to it.Convenience initializer
EnumCaseParameterSyntax.init()EnumCaseParameterSyntaxthat takes a concretefirstNamevalue and addscolon = TokenSyntax.colonToken()automatically to it.DiagnosticSeverityandPluginMessage.Diagnostic.Severitynow have new case namedremarkDeprecations
Leaf Node Casts
Same-Type Casts
is,as, andcastoverloads onSyntaxProtocolwith same-type conversions are marked as deprecated. The deprecated methods emit a warning indicating the cast will always succeed.Base Node Casts
is,as, andcastmethods on base node protocols with base-type conversions are marked as deprecated. The deprecated methods emit a warning that informs the developer that the cast will always succeed and should be done using the base node's initializer.WildcardPatternSyntax.typeAnnotationtypeAnnotationonWildcardPatternSyntaxwas a mistake. UsetypeAnnotationproperties on the outer constructs instead. E.g.PatternBindingListSyntax.typeAnnotationAPI-Incompatible Changes
NoteMessage.fixItIDrenamed tonoteIDfixItIDand should have been namednoteIDinstead. Accesses tofixItIDare deprecated and forward tonoteID. Any types that conformNoteMessageit will need to be updated to provide anoteIDinstead of afixItID.DiagnosticSpec.highlightreplaced byhighlightshighlightprevented users from asserting that a macro highlighted exactly the expected set of syntax nodes. Use ofDiagnosticSpec.init(...highlight:...)is deprecated and forwards toDiagnosticSpec.init(...highlights:...). Migrating fromhighlighttohighlightsis straightforward; any uses ofDiagnosticSpec.initwhich do not specify ahighlightdo not need to change, otherwise:highlightstring should be replaced with a single element array containing the same string without any trailing trivia, e.g.,highlight: "let "->highlights: ["let"].highlightstring should be replaced with an array containing an element for each highlighted node, e.g.,highlight: "struct {}"->highlights: ["struct", "{}"].v510.0.2Compare Source
Compared to 510.0.1 this release fixes compilation warnings about retroactive conformances when building swift-syntax with a Swift 6 compiler.
It also contains the following changes from 510.0.0.
New APIs
SyntaxStringInterpolation.appendInterpolation(_: (some SyntaxProtocol)?)nil, nothing will get added to the string interpolation.SyntaxCollection.index(at:)SyntaxCollection. This computation is in O(n) andSyntaxCollectionis not subscriptable by an integer.Convenience initializer
ClosureCaptureSyntax.init()ClosureCaptureSyntaxthat takes a concretenameargument and automatically addsequal = TokenSyntax.equalToken()to it.Convenience initializer
EnumCaseParameterSyntax.init()EnumCaseParameterSyntaxthat takes a concretefirstNamevalue and addscolon = TokenSyntax.colonToken()automatically to it.DiagnosticSeverityandPluginMessage.Diagnostic.Severitynow have new case namedremarkDeprecations
Leaf Node Casts
Same-Type Casts
is,as, andcastoverloads onSyntaxProtocolwith same-type conversions are marked as deprecated. The deprecated methods emit a warning indicating the cast will always succeed.Base Node Casts
is,as, andcastmethods on base node protocols with base-type conversions are marked as deprecated. The deprecated methods emit a warning that informs the developer that the cast will always succeed and should be done using the base node's initializer.WildcardPatternSyntax.typeAnnotationtypeAnnotationonWildcardPatternSyntaxwas a mistake. UsetypeAnnotationproperties on the outer constructs instead. E.g.PatternBindingListSyntax.typeAnnotationAPI-Incompatible Changes
NoteMessage.fixItIDrenamed tonoteIDfixItIDand should have been namednoteIDinstead. Accesses tofixItIDare deprecated and forward tonoteID. Any types that conformNoteMessageit will need to be updated to provide anoteIDinstead of afixItID.DiagnosticSpec.highlightreplaced byhighlightshighlightprevented users from asserting that a macro highlighted exactly the expected set of syntax nodes. Use ofDiagnosticSpec.init(...highlight:...)is deprecated and forwards toDiagnosticSpec.init(...highlights:...). Migrating fromhighlighttohighlightsis straightforward; any uses ofDiagnosticSpec.initwhich do not specify ahighlightdo not need to change, otherwise:highlightstring should be replaced with a single element array containing the same string without any trailing trivia, e.g.,highlight: "let "->highlights: ["let"].highlightstring should be replaced with an array containing an element for each highlighted node, e.g.,highlight: "struct {}"->highlights: ["struct", "{}"].v510.0.1Compare Source
Compared to 510.0.0 this fixes a possible misaligned memory access.
It also contains the following changes from 510.0.0.
New APIs
SyntaxStringInterpolation.appendInterpolation(_: (some SyntaxProtocol)?)nil, nothing will get added to the string interpolation.SyntaxCollection.index(at:)SyntaxCollection. This computation is in O(n) andSyntaxCollectionis not subscriptable by an integer.Convenience initializer
ClosureCaptureSyntax.init()ClosureCaptureSyntaxthat takes a concretenameargument and automatically addsequal = TokenSyntax.equalToken()to it.Convenience initializer
EnumCaseParameterSyntax.init()EnumCaseParameterSyntaxthat takes a concretefirstNamevalue and addscolon = TokenSyntax.colonToken()automatically to it.DiagnosticSeverityandPluginMessage.Diagnostic.Severitynow have new case namedremarkDeprecations
Leaf Node Casts
Same-Type Casts
is,as, andcastoverloads onSyntaxProtocolwith same-type conversions are marked as deprecated. The deprecated methods emit a warning indicating the cast will always succeed.Base Node Casts
is,as, andcastmethods on base node protocols with base-type conversions are marked as deprecated. The deprecated methods emit a warning that informs the developer that the cast will always succeed and should be done using the base node's initializer.WildcardPatternSyntax.typeAnnotationtypeAnnotationonWildcardPatternSyntaxwas a mistake. UsetypeAnnotationproperties on the outer constructs instead. E.g.PatternBindingListSyntax.typeAnnotationAPI-Incompatible Changes
NoteMessage.fixItIDrenamed tonoteIDfixItIDand should have been namednoteIDinstead. Accesses tofixItIDare deprecated and forward tonoteID. Any types that conformNoteMessageit will need to be updated to provide anoteIDinstead of afixItID.DiagnosticSpec.highlightreplaced byhighlightshighlightprevented users from asserting that a macro highlighted exactly the expected set of syntax nodes. Use ofDiagnosticSpec.init(...highlight:...)is deprecated and forwards toDiagnosticSpec.init(...highlights:...). Migrating fromhighlighttohighlightsis straightforward; any uses ofDiagnosticSpec.initwhich do not specify ahighlightdo not need to change, otherwise:highlightstring should be replaced with a single element array containing the same string without any trailing trivia, e.g.,highlight: "let "->highlights: ["let"].highlightstring should be replaced with an array containing an element for each highlighted node, e.g.,highlight: "struct {}"->highlights: ["struct", "{}"].v510.0.0Compare Source
New APIs
SyntaxStringInterpolation.appendInterpolation(_: (some SyntaxProtocol)?)nil, nothing will get added to the string interpolation.SyntaxCollection.index(at:)SyntaxCollection. This computation is in O(n) andSyntaxCollectionis not subscriptable by an integer.Convenience initializer
ClosureCaptureSyntax.init()ClosureCaptureSyntaxthat takes a concretenameargument and automatically addsequal = TokenSyntax.equalToken()to it.Convenience initializer
EnumCaseParameterSyntax.init()EnumCaseParameterSyntaxthat takes a concretefirstNamevalue and addscolon = TokenSyntax.colonToken()automatically to it.DiagnosticSeverityandPluginMessage.Diagnostic.Severitynow have new case namedremarkDeprecations
Leaf Node Casts
Same-Type Casts
is,as, andcastoverloads onSyntaxProtocolwith same-type conversions are marked as deprecated. The deprecated methods emit a warning indicating the cast will always succeed.Base Node Casts
is,as, andcastmethods on base node protocols with base-type conversions are marked as deprecated. The deprecated methods emit a warning that informs the developer that the cast will always succeed and should be done using the base node's initializer.WildcardPatternSyntax.typeAnnotationtypeAnnotationonWildcardPatternSyntaxwas a mistake. UsetypeAnnotationproperties on the outer constructs instead. E.g.PatternBindingListSyntax.typeAnnotationAPI-Incompatible Changes
NoteMessage.fixItIDrenamed tonoteIDfixItIDand should have been namednoteIDinstead. Accesses tofixItIDare deprecated and forward tonoteID. Any types that conformNoteMessageit will need to be updated to provide anoteIDinstead of afixItID.DiagnosticSpec.highlightreplaced byhighlightshighlightprevented users from asserting that a macro highlighted exactly the expected set of syntax nodes. Use ofDiagnosticSpec.init(...highlight:...)is deprecated and forwards toDiagnosticSpec.init(...highlights:...). Migrating fromhighlighttohighlightsis straightforward; any uses ofDiagnosticSpec.initwhich do not specify ahighlightdo not need to change, otherwise:highlightstring should be replaced with a single element array containing the same string without any trailing trivia, e.g.,highlight: "let "->highlights: ["let"].highlightstring should be replaced with an array containing an element for each highlighted node, e.g.,highlight: "struct {}"->highlights: ["struct", "{}"].v509.1.1Compare Source
Fixes an issue that caused the
swift-parser-clitarget to not build on visionOS.v509.1.0Compare Source
expansionfunction inMemberMacrothat receives theconformingToparameterConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.