-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Add optional return_value_from_void_function rule using SwiftSyntax #3054
Merged
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
marcelofabri
force-pushed
the
mf-return_value_from_void_function
branch
2 times, most recently
from
February 3, 2020 01:03
38706a8
to
af4b40a
Compare
This was referenced Feb 3, 2020
marcelofabri
force-pushed
the
mf-return_value_from_void_function
branch
from
February 8, 2020 10:06
b0c1ec9
to
1e6dc6c
Compare
2 tasks
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.
See #3015
This adds SwiftSyntax as a submodule, which should workaround an issue with SPM + Xcode, while keeping development flow similar.
We could move everything to SPM, but that's more work that I can handle now, so I hope we can move forward with this PR, which will enable using
SwiftSyntax
to create more complex rules.This rule is opt-in because it's slower than the other ones.