[SR-11167] Ensure space between someSpecifier and baseType in SomeTypeSyntax
#10
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
kitasuke
changed the title
someSpecifier and baseType in SomeTypeSyntaxsomeSpecifier and baseType in SomeTypeSyntax
allevato
approved these changes
Jul 20, 2019
aaditya-chandrasekhar
pushed a commit
to val-verde/swift-format
that referenced
this pull request
May 20, 2021
README: Corrections for three minor typos
xymus
pushed a commit
to xymus/swift-format
that referenced
this pull request
Aug 14, 2023
…ission-rules [Lint] Omit `return` if body of a function, closure or subscript getter consists of a single expression
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.
Produced source code with
SomeTypeSyntaxis not compilable because there is no space in the syntaxFixes SR-11167.