Conversation
`key = value` is not a valid significant test comment form, the value must be `Block` not double-quoted `"block"` or `"Block"`.
Member
This is an idempotence test. There are many tests that are this way. It just requires rustfmt does not change the test. |
Member
Author
|
Ah, my apologies, that wasn't super obvious. I'll drop that commit. |
fee1-dead
approved these changes
Oct 8, 2025
ytmimi
approved these changes
Oct 8, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Noticed while trying to figure out #6681. cf. #t-rustfmt > Is `// rustfmt-* = value` a valid "significant" test comment.
tests/source/issue-1278.rstest headers:key = valueis not a valid significant test comment form, the value must beBlocknot double-quoted"block"or"Block".