-
Notifications
You must be signed in to change notification settings - Fork 13.3k
tidy watcher #114209
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?
tidy watcher #114209
Changes from all commits
b463c07
dbc585e
37de857
829b88d
7a86644
31ee3e2
1d4c9a1
09aa084
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -177,6 +177,7 @@ pub(crate) fn default_configuration(sess: &Session) -> Cfg { | |
// | ||
// NOTE: These insertions should be kept in sync with | ||
// `CheckCfg::fill_well_known` below. | ||
// FIXME: sync me | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Is it possible to still apply this tidy annotation in that case ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This pr/feature can only assert that some spans unchanged, nothing more. It's up to author/reviewer check actual content. Should i wrap entire default_configuration/fill_well_known fns? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In that case, yes, you can wrap them (if you want, of course). |
||
|
||
if sess.opts.debug_assertions { | ||
ins_none!(sym::debug_assertions); | ||
|
@@ -340,6 +341,7 @@ impl CheckCfg { | |
// The exceptions are where control flow forces things out of order. | ||
// | ||
// NOTE: This should be kept in sync with `default_configuration`. | ||
// FIXME: what exactly sync there? | ||
// Note that symbols inserted conditionally in `default_configuration` | ||
// are inserted unconditionally here. | ||
// | ||
|
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.
This one is a semantic sync rather than a data sync, and violating it would cause a bunch of tests to break, so it's probably not worth the hassle of adding sync-check tags here.