-
Notifications
You must be signed in to change notification settings - Fork 12
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
Tracking upstream bugs #5
Comments
keith
added a commit
that referenced
this issue
Mar 28, 2023
This tool uses the index data to suggest imports that can be removed from your files. Currently compared to SwiftLint's implementation it's much faster, but doesn't yet add missing imports, or remove unused system imports. It's currently lightly affected by upstream issues listed here #5
keith
added a commit
that referenced
this issue
Mar 29, 2023
This tool uses the index data to suggest imports that can be removed from your files. Currently compared to SwiftLint's implementation it's much faster, but doesn't yet add missing imports, or remove unused system imports. It's currently lightly affected by upstream issues listed here #5
keith
added a commit
that referenced
this issue
Apr 5, 2023
This tool uses the index data to suggest imports that can be removed from your files. Currently compared to SwiftLint's implementation it's much faster, but doesn't yet add missing imports, or remove unused system imports. It's currently lightly affected by upstream issues listed here #5
keith
added a commit
that referenced
this issue
Apr 5, 2023
This tool uses the index data to suggest imports that can be removed from your files. Currently compared to SwiftLint's implementation it's much faster, but doesn't yet add missing imports, or remove unused system imports. It's currently lightly affected by upstream issues listed here #5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is just a place to link upstream bugs in Swift that might affect the output of this tool. Here are the ones I currently know about:
(I haven't recently verified the older issues there, so it's possible those are fixed, if so it would be nice to verify and close them upstream)
The text was updated successfully, but these errors were encountered: