-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Report usage of lib features in ast validation #127587
Conversation
Actually, we don't halt compilation if we hit a feature-on-stable error? (At least afaict??) So the warning that we currently issue for a library feature that is already stable is still there. I don't actually think there's any regression here at all. |
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.
ok, this was quite confusing, but I got it eventually.
originally, all the check for whether we're using feature on stable was in ast_passes.
then, it got split, where it's checked in ast_passes when there are lang features, and not in ast_passes when there are any no lang features.
when there are no lang features, it still did a check for libs features specifically in the later pass.
this improved a diagnostic for libs features, but made the code quite confusing (as evidenced by my confusion).
so now you basically just revert that and make it nice again, where everything is checked in ast_passes.
good!
@bors r+ |
and don't forget to reopen the issue! |
Wait, did you see my last comment? I don't think this regresses the issue. I will just add a test. @bors r- |
uh, right. yeah. |
It did in fact not regress:
But also I can't add a test for it because we don't error for @bors r=Nilstrieb |
…iaskrgr Rollup of 5 pull requests Successful merges: - rust-lang#127273 (Fix `DebugParser`.) - rust-lang#127587 (Report usage of lib features in ast validation) - rust-lang#127592 (doc: Suggest `str::repeat` over `iter::repeat().take().collect()`) - rust-lang#127630 (Remove lang feature for type ascription (since it's a lib feature now)) - rust-lang#127711 (Add regression test for a gce + effects ICE) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#127587 - compiler-errors:all-features-at-once, r=Nilstrieb Report usage of lib features in ast validation No idea why it was split between ast validation for lang features and a later pass for lang features. r? `@Nilstrieb`
No idea why it was split between ast validation for lang features and a later pass for lang features.
r? @Nilstrieb