-
Notifications
You must be signed in to change notification settings - Fork 441
Parse an ellipsis T...
for type parameter packs
#948
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -145,6 +145,29 @@ public class ParseDiagnosticsGenerator: SyntaxAnyVisitor { | |
addDiagnostic(incorrectContainer, message(misplacedTokens), fixIts: fixIts, handledNodes: [incorrectContainer.id] + correctAndMissingTokens.map(\.id)) | ||
} | ||
|
||
/// Utility function to remove a misplaced token with a custom error message. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If you agree, I think the following comment is a little more descriptive. /// If `unexpected` only contains a single token that satisfies `predicate` emit a diagnostic with `message` that removes this token. |
||
public func removeToken( | ||
_ unexpected: UnexpectedNodesSyntax?, | ||
where predicate: (TokenSyntax) -> Bool, | ||
message: (TokenSyntax) -> DiagnosticMessage | ||
) { | ||
guard let unexpected = unexpected, | ||
let misplacedToken = unexpected.onlyToken(where: predicate) | ||
else { | ||
// If there is no unexpected node or the unexpected doesn't have the | ||
// expected token, don't emit a diagnostic. | ||
return | ||
} | ||
let fixit = FixIt( | ||
message: RemoveNodesFixIt(unexpected), | ||
changes: [.remove(unexpected: unexpected)] | ||
) | ||
addDiagnostic( | ||
unexpected, message(misplacedToken), fixIts: [fixit], | ||
handledNodes: [unexpected.id] | ||
) | ||
} | ||
|
||
// MARK: - Generic diagnostic generation | ||
|
||
public override func visitAny(_ node: Syntax) -> SyntaxVisitorContinueKind { | ||
|
@@ -563,6 +586,20 @@ public class ParseDiagnosticsGenerator: SyntaxAnyVisitor { | |
return .visitChildren | ||
} | ||
|
||
public override func visit(_ node: AssociatedtypeDeclSyntax) -> SyntaxVisitorContinueKind { | ||
if shouldSkip(node) { | ||
return .skipChildren | ||
} | ||
// Emit a custom diagnostic for an unexpected '...' after an associatedtype | ||
// name. | ||
removeToken( | ||
node.unexpectedBetweenIdentifierAndInheritanceClause, | ||
where: { $0.tokenKind == .ellipsis }, | ||
message: { _ in StaticParserError.associatedTypeCannotUsePack } | ||
) | ||
return .visitChildren | ||
} | ||
|
||
public override func visit(_ node: VariableDeclSyntax) -> SyntaxVisitorContinueKind { | ||
if shouldSkip(node) { | ||
return .skipChildren | ||
|
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a convenience initializer on
RawUnexpectedNodesSyntax
that fails if it is passed only nil elements, so this can be simplified toand then below where you are currently passing
unexpectedAfterName
to theRawAssociatedtypeDeclSyntax
initializer:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Neat!