Gardening: Migrate compiler sources to GitHub issues #61347
Merged
Conversation
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
xedin
reviewed
Sep 29, 2022
AnthonyLatsis
force-pushed
the
migrate-compiler-to-gh-issues
branch
from
5ca7c79 to
2843e0c
Compare
xedin
approved these changes
Sep 29, 2022
|
@swift-ci please test |
|
@swift-ci please test Windows |
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.
I am intentionally violating the 80 char limit in a lot of places here. The idea is for
TODOandFIXMEto show up nicely in search results, context and all, no truncation. Doesn’t look too bad with line wrapping enabled. Also, perhaps unfortunately, Xcode doesn’t pick up onTODO(...):orFIXME(...):. Thoughts?