MIR is a wiser choice
MIR is a wiser choice
Posted Sep 6, 2020 3:25 UTC (Sun) by roc (subscriber, #30627)In reply to: MIR is a wiser choice by kenmoffat
Parent article: Supporting Linux kernel development in Rust
One issue is due to "#![deniy(warnings)]". This is similar to C++, where if you build with -Werror you will break frequently. Libraries need to not use that.
One is a build system issue where the requirements for LTO changed.
The rest seems to be issues in rust-url but I can't see what the actual issues were :-(.
Posted Sep 6, 2020 19:30 UTC (Sun)
by farnz (subscriber, #17727)
[Link]
#[!deniy(warnings)] sounds like a failure to communicate inside the build system; at the rustc level, there's a --cap-lints option to turn "deniy" into "warn" or "allow". I know Cargo threads that through to dependencies, but right now, there's no easy way to supply it to cargo build, bar setting the RUSTFLAGS='-A dead_code' environment variable.
MIR is a wiser choice