-
Notifications
You must be signed in to change notification settings - Fork 13.7k
test(rustfmt): Verify frontmatter is preserved #145766
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
base: master
Are you sure you want to change the base?
Conversation
This is to prove that the frontmatter is preserved. The choices in tests is intended for showing the different parts of the proposed Style Guide for frontmatters.
rustbot has assigned @Mark-Simulacrum. Use |
Some changes occurred in src/tools/rustfmt cc @rust-lang/rustfmt |
The job Click to see the possible cause of the failure (guessed by this bot)
|
--- | ||
#![feature(frontmatter)] | ||
|
||
fn main() {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this check that the file as a whole is being formatted? I think rustfmt sometimes bails out on formatting just from the presence somewhere in the file of syntax... not sure if that's happening here or not (or quite what the test format here looks like).
It probably makes sense to try to get rustfmt team review (do you have someone to re-assign already?). Otherwise, if we think that's not feasible, happy to just rubberstamp.
Probably worth rolling a rustfmt reviewer |
This is to prove that the frontmatter is preserved.
The choices in tests is intended for showing the different parts of the proposed Style Guide for frontmatters (#145617).
While rustfmt is developed in a different repo, work involving upstream integration is blocked on some work that is being finished up in that repo. I was told that it would be ok to post against this repo in the mean time.
Tracking issue: #136889