chore(deps): update dependency apple/swift-syntax to v510 - autoclosed #31
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:
0.50100.0
->510.0.3
Release Notes
apple/swift-syntax (apple/swift-syntax)
v510.0.3
Compare 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) andSyntaxCollection
is not subscriptable by an integer.Convenience initializer
ClosureCaptureSyntax.init()
ClosureCaptureSyntax
that takes a concretename
argument and automatically addsequal = TokenSyntax.equalToken()
to it.Convenience initializer
EnumCaseParameterSyntax.init()
EnumCaseParameterSyntax
that takes a concretefirstName
value and addscolon = TokenSyntax.colonToken()
automatically to it.DiagnosticSeverity
andPluginMessage.Diagnostic.Severity
now have new case namedremark
Deprecations
Leaf Node Casts
Same-Type Casts
is
,as
, andcast
overloads onSyntaxProtocol
with same-type conversions are marked as deprecated. The deprecated methods emit a warning indicating the cast will always succeed.Base Node Casts
is
,as
, andcast
methods 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.typeAnnotation
typeAnnotation
onWildcardPatternSyntax
was a mistake. UsetypeAnnotation
properties on the outer constructs instead. E.g.PatternBindingListSyntax.typeAnnotation
API-Incompatible Changes
NoteMessage.fixItID
renamed tonoteID
fixItID
and should have been namednoteID
instead. Accesses tofixItID
are deprecated and forward tonoteID
. Any types that conformNoteMessage
it will need to be updated to provide anoteID
instead of afixItID
.DiagnosticSpec.highlight
replaced byhighlights
highlight
prevented 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 fromhighlight
tohighlights
is straightforward; any uses ofDiagnosticSpec.init
which do not specify ahighlight
do not need to change, otherwise:highlight
string should be replaced with a single element array containing the same string without any trailing trivia, e.g.,highlight: "let "
->highlights: ["let"]
.highlight
string should be replaced with an array containing an element for each highlighted node, e.g.,highlight: "struct {}"
->highlights: ["struct", "{}"]
.v510.0.2
Compare 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) andSyntaxCollection
is not subscriptable by an integer.Convenience initializer
ClosureCaptureSyntax.init()
ClosureCaptureSyntax
that takes a concretename
argument and automatically addsequal = TokenSyntax.equalToken()
to it.Convenience initializer
EnumCaseParameterSyntax.init()
EnumCaseParameterSyntax
that takes a concretefirstName
value and addscolon = TokenSyntax.colonToken()
automatically to it.DiagnosticSeverity
andPluginMessage.Diagnostic.Severity
now have new case namedremark
Deprecations
Leaf Node Casts
Same-Type Casts
is
,as
, andcast
overloads onSyntaxProtocol
with same-type conversions are marked as deprecated. The deprecated methods emit a warning indicating the cast will always succeed.Base Node Casts
is
,as
, andcast
methods 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.typeAnnotation
typeAnnotation
onWildcardPatternSyntax
was a mistake. UsetypeAnnotation
properties on the outer constructs instead. E.g.PatternBindingListSyntax.typeAnnotation
API-Incompatible Changes
NoteMessage.fixItID
renamed tonoteID
fixItID
and should have been namednoteID
instead. Accesses tofixItID
are deprecated and forward tonoteID
. Any types that conformNoteMessage
it will need to be updated to provide anoteID
instead of afixItID
.DiagnosticSpec.highlight
replaced byhighlights
highlight
prevented 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 fromhighlight
tohighlights
is straightforward; any uses ofDiagnosticSpec.init
which do not specify ahighlight
do not need to change, otherwise:highlight
string should be replaced with a single element array containing the same string without any trailing trivia, e.g.,highlight: "let "
->highlights: ["let"]
.highlight
string should be replaced with an array containing an element for each highlighted node, e.g.,highlight: "struct {}"
->highlights: ["struct", "{}"]
.v510.0.1
Compare 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) andSyntaxCollection
is not subscriptable by an integer.Convenience initializer
ClosureCaptureSyntax.init()
ClosureCaptureSyntax
that takes a concretename
argument and automatically addsequal = TokenSyntax.equalToken()
to it.Convenience initializer
EnumCaseParameterSyntax.init()
EnumCaseParameterSyntax
that takes a concretefirstName
value and addscolon = TokenSyntax.colonToken()
automatically to it.DiagnosticSeverity
andPluginMessage.Diagnostic.Severity
now have new case namedremark
Deprecations
Leaf Node Casts
Same-Type Casts
is
,as
, andcast
overloads onSyntaxProtocol
with same-type conversions are marked as deprecated. The deprecated methods emit a warning indicating the cast will always succeed.Base Node Casts
is
,as
, andcast
methods 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.typeAnnotation
typeAnnotation
onWildcardPatternSyntax
was a mistake. UsetypeAnnotation
properties on the outer constructs instead. E.g.PatternBindingListSyntax.typeAnnotation
API-Incompatible Changes
NoteMessage.fixItID
renamed tonoteID
fixItID
and should have been namednoteID
instead. Accesses tofixItID
are deprecated and forward tonoteID
. Any types that conformNoteMessage
it will need to be updated to provide anoteID
instead of afixItID
.DiagnosticSpec.highlight
replaced byhighlights
highlight
prevented 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 fromhighlight
tohighlights
is straightforward; any uses ofDiagnosticSpec.init
which do not specify ahighlight
do not need to change, otherwise:highlight
string should be replaced with a single element array containing the same string without any trailing trivia, e.g.,highlight: "let "
->highlights: ["let"]
.highlight
string should be replaced with an array containing an element for each highlighted node, e.g.,highlight: "struct {}"
->highlights: ["struct", "{}"]
.v510.0.0
Compare 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) andSyntaxCollection
is not subscriptable by an integer.Convenience initializer
ClosureCaptureSyntax.init()
ClosureCaptureSyntax
that takes a concretename
argument and automatically addsequal = TokenSyntax.equalToken()
to it.Convenience initializer
EnumCaseParameterSyntax.init()
EnumCaseParameterSyntax
that takes a concretefirstName
value and addscolon = TokenSyntax.colonToken()
automatically to it.DiagnosticSeverity
andPluginMessage.Diagnostic.Severity
now have new case namedremark
Deprecations
Leaf Node Casts
Same-Type Casts
is
,as
, andcast
overloads onSyntaxProtocol
with same-type conversions are marked as deprecated. The deprecated methods emit a warning indicating the cast will always succeed.Base Node Casts
is
,as
, andcast
methods 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.typeAnnotation
typeAnnotation
onWildcardPatternSyntax
was a mistake. UsetypeAnnotation
properties on the outer constructs instead. E.g.PatternBindingListSyntax.typeAnnotation
API-Incompatible Changes
NoteMessage.fixItID
renamed tonoteID
fixItID
and should have been namednoteID
instead. Accesses tofixItID
are deprecated and forward tonoteID
. Any types that conformNoteMessage
it will need to be updated to provide anoteID
instead of afixItID
.DiagnosticSpec.highlight
replaced byhighlights
highlight
prevented 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 fromhighlight
tohighlights
is straightforward; any uses ofDiagnosticSpec.init
which do not specify ahighlight
do not need to change, otherwise:highlight
string should be replaced with a single element array containing the same string without any trailing trivia, e.g.,highlight: "let "
->highlights: ["let"]
.highlight
string should be replaced with an array containing an element for each highlighted node, e.g.,highlight: "struct {}"
->highlights: ["struct", "{}"]
.v509.1.1
Compare Source
Fixes an issue that caused the
swift-parser-cli
target to not build on visionOS.v509.1.0
Compare Source
expansion
function inMemberMacro
that receives theconformingTo
parameterv509.0.2
Compare Source
Fixes a possible misaligned memory access
v509.0.1
Compare Source
Fixes the following issues:
Foo<T>.bar
should not have whitespace added between>
and.
(https://github.com/apple/swift-syntax/pull/2224)SwiftSyntaxMacroExpansion
andSwiftOperators
(https://github.com/apple/swift-syntax/pull/2224)v509.0.0
Compare Source
This is the 509.0.0 release of SwiftSyntax, aligned with Swift 5.9.
To use this snapshot add the following dependency to your Package.swift:
v508.0.1
Compare Source
This release of SwiftSyntax is aligned with the release of Swift 5.8.
Compared to 508.0.0, this release relaxes the version requirement for
swift-argument-parser
, resulting in fewer version conflicts for users of SwiftSyntax.v508.0.0
Compare Source
This is the 508.0.0 release of SwiftSyntax, aligned with the release of Swift 5.8.
To use this snapshot add the following dependency to your Package.swift:
v0.50700.1
Compare Source
This is the 0.50700.1 release of SwiftSyntax that vends the parser library (
_InternalSwiftSyntaxParser.dylib
) as a binary framework dependency on macOS.To use this snapshot add the following dependency to your Package.swift:
Or, if using a swift-tools-version ≤ 5.4:
v0.50700.0
Compare Source
This is the 0.50700.0 release of SwiftSyntax that vends the parser library (
_InternalSwiftSyntaxParser.dylib
) as a binary framework dependency on macOS.To use this snapshot add the following dependency to your Package.swift:
Or, if using a swift-tools-version ≤ 5.4:
v0.50600.1
Compare Source
This is the 0.50600.1 release of SwiftSyntax that vends the parser library (
_InternalSwiftSyntaxParser.dylib
) as a binary framework dependency on macOS.To use this snapshot add the following dependency to your Package.swift:
Or, if using a swift-tools-version ≤ 5.4:
v0.50600.0
Compare Source
This is the 0.50600.0 release of SwiftSyntax that vends the parser library (
_InternalSwiftSyntaxParser.dylib
) as a binary framework dependency on macOS.To use this snapshot add the following dependency to your Package.swift:
Or, if using a swift-tools-version ≤ 5.4:
v0.50500.0
Compare Source
v0.50400.0
Compare Source
v0.50300.0
Compare Source
v0.50200.0
Compare Source
Configuration
📅 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.