-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
remove build warnings #71303
remove build warnings #71303
Conversation
Code blocks that are not annotated are assumed to be Rust
r? @varkor (rust_highfive has picked a reviewer for you, use r? to override) |
It sounds like there's an underlying bug here as well, as we should always be running with warnings denied in CI. Can you say which command you're running that's printing warnings? |
It probably was |
Hm. Odd. Anyway, @bors r+ rollup for now, but would be good to track that down. |
📌 Commit fcbefae has been approved by |
@Mark-Simulacrum I was actually surprised by the warnings, given there's no |
Rollup of 5 pull requests Successful merges: - rust-lang#71271 (Move `MapInPlace` to rustc_data_structures) - rust-lang#71276 (miri-unleashed: test that we detect heap allocations) - rust-lang#71283 (Minor improvements to -Zprofile) - rust-lang#71287 (Explain why we shouldn't add inline attr to into_vec) - rust-lang#71303 (remove build warnings) Failed merges: r? @ghost
Actually I think I saw those warnings because I was running |
Code blocks that are not annotated are assumed to be Rust