Skip to content

Conversation

@JTurcotti
Copy link
Contributor

This @ being unescaped throws a LOT of spurious warnings during build.

@JTurcotti
Copy link
Contributor Author

@swift-ci please smoke test

Copy link
Contributor

@beccadax beccadax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn’t worth rejecting the PR, but for future reference, we usually put [NFC] at the beginning of the message when a commit makes No Functional Changes (fixes comments or formatting, refactors without a behavior change, adds tests of existing behavior, etc.).

Otherwise LGTM.

@JTurcotti JTurcotti changed the title Escape an @ that throws spurious warnings [NFC] Escape an @ that throws spurious warnings Jun 29, 2023
@JTurcotti
Copy link
Contributor Author

thanks for the tip @beccadax ! modified PR message but next time will include in commit message too

@JTurcotti
Copy link
Contributor Author

@swift-ci please merge

@JTurcotti
Copy link
Contributor Author

@swift-ci please smoke test

3 similar comments
@JTurcotti
Copy link
Contributor Author

@swift-ci please smoke test

@JTurcotti
Copy link
Contributor Author

@swift-ci please smoke test

@JTurcotti
Copy link
Contributor Author

@swift-ci please smoke test

@JTurcotti
Copy link
Contributor Author

addressed by #66915

@JTurcotti JTurcotti closed this Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants