-
Notifications
You must be signed in to change notification settings - Fork 13.6k
add unsupported_calling_conventions to lint list #144772
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
add unsupported_calling_conventions to lint list #144772
Conversation
@bors r+ |
(Could be good to have this exercised in a test in a future PR, not this one since it's somewhat urgent) |
(Backports are handled by @rust-lang/release not infra) |
@rust-lang/release this should be included in 1.89 |
I mean then we should have tests like this for all lints... |
Beta-backport accepted as discussed in #t-compiler/backports > #144772: beta-nominated. @rustbot label: +beta-accepted |
Rollup of 6 pull requests Successful merges: - #144397 (`tests/ui/issues/`: The Issues Strike Back [2/N]) - #144410 (Make tier 3 musl targets link dynamically by default) - #144708 (Add tracing to step.rs and friends) - #144730 (Create a typed wrapper for codegen backends in bootstrap) - #144771 (Remove some noisy triagebot pings for myself) - #144772 (add unsupported_calling_conventions to lint list) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of #144772 - RalfJung:unsupported_calling_conventions, r=lqd add unsupported_calling_conventions to lint list Seems like you can emit lints without them being on the list, but users cannot control them then... *oops*.
Seems like you can emit lints without them being on the list, but users cannot control them then... oops.